prelink

According to [1], prelink is no longer needed.

When I configure wine-1.9.6, I get the warning message,
"configure: WARNING: prelink not found and linker does not support 
relocation, base address of core dlls won't be set correctly."

[1] http://oldwiki.winehq.org/Prelink

[Kyle Auble]

On 03/19/2016 05:27 PM, [e-mail] wrote:
> According to [1], prelink is no longer needed.
>
> When I configure wine-1.9.6, I get the warning message,
> "configure: WARNING: prelink not found and linker does not support 
> relocation, base address of core dlls won't be set correctly."
>
> [1] http://oldwiki.winehq.org/Prelink

Hi there,

So I'm not one of the devs but my first question would be are your 
build-tools (specifically the linker, "ld" for gnu or "lld" for clang) 
relatively up-to-date? Prelink used to be the default way to set the 
DLLs in a specific memory location (for the occasional program that 
expects that), but prelink brings a lot of baggage with it.

I think Fedora actually stopped packaging prelink altogether a while 
back, and I know Debian no longer builds their wine packages with it. 
Apparently there are other ways to solve any problem that prelink can, 
but you also need some newer linker features.

For a little background, here's a mailing-list discussion...
https://www.winehq.org/pipermail/wine-devel/2015-August/108695.html
... and here's the patch that explains your warning message:
http://source.winehq.org/git/wine.git/commit/a35f9a13a80fa93c251e12402a73a38...

Kyle

[Nathan]

Kyle Auble wrote:
> Hi there,
>
> So I'm not one of the devs but my first question would be are your 
> build-tools (specifically the linker, "ld" for gnu or "lld" for clang) 
> relatively up-to-date? Prelink used to be the default way to set the 
> DLLs in a specific memory location (for the occasional program that 
> expects that), but prelink brings a lot of baggage with it.
>
> I think Fedora actually stopped packaging prelink altogether a while 
> back, and I know Debian no longer builds their wine packages with it. 
> Apparently there are other ways to solve any problem that prelink can, 
> but you also need some newer linker features.
>
> For a little background, here's a mailing-list discussion...
> https://www.winehq.org/pipermail/wine-devel/2015-August/108695.html
> ... and here's the patch that explains your warning message:
> http://source.winehq.org/git/wine.git/commit/a35f9a13a80fa93c251e12402a73a38...
>
> Kyle

Marcus Meissner wrote:
> This means your binutils version might not yet support the -Wl,-Ttext-segment option.
>
> Ciao, Marcus

Thanks for the information and links.

A distro I compile in:

ld --version
GNU ld (Linux/GNU Binutils) 2.18.50.0.2.20071001
Copyright 2007 Free Software Foundation, Inc.

Another distro I compile in:

ld --version
GNU ld (Linux/GNU Binutils) 2.20.51.0.2.20091009
Copyright 2009 Free Software Foundation, Inc

It is good to know that when I decide to compile with a newer version of 
my distro, with the included updated 'GNU ld', I will no longer need 
prelink.

Nathan

[Marcus Meissner]

On Sat, Mar 19, 2016 at 07:27:10PM -0400, [e-mail] wrote:
> According to [1], prelink is no longer needed.
>
> When I configure wine-1.9.6, I get the warning message,
> "configure: WARNING: prelink not found and linker does not support
> relocation, base address of core dlls won't be set correctly."

This means your binutils version might not yet support the -Wl,-Ttext-segment option.

Ciao, Marcus