[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Question about relink_command

From: Gary V. Vaughan
Subject: Re: Question about relink_command
Date: Mon, 31 May 2010 22:53:26 +0700

On May 31, 2010, at 5:11 PM, Alex Farber <address@hidden> wrote:

Sorry, I didn't understand the question. I just tried installation without relink_command, by removing relink_command from .la file, and it works. So, I wanted to know when it is really necessary.

On Mon, May 31, 2010 at 10:29 AM, Tor Lillqvist <address@hidden> wrote:
What makes you think the issue relinking is related to would have
anything to do with Linux in particular?


AFAIK Linux binaries/libraries can be built in the build tree with no hardcoded references to other objects in the build tree, so they can always be copied into the install tree and continue working (although libtool has to wrap build tree binaries in a script to make sure that running them there picks up build tree libraries in preference to install tree libraries).

On some architectures, notably HP-UX, when you link a binary against a build tree library and then copy it to the install tree, it still has references to the build tree left behind by the linker (stored in $hardcoded_into_libs IIRC). In cases like this, libtool installs the libraries and then relinks binaries against the install tree libraries before installing them.

As an added bonus, if you know that you won't be running the binaries in the build tree (say, to run the package testsuite), you can specify --fast-install at configure time to always do the initial link against install tree paths.

Gary V. Vaughan (address@hidden)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]