[Top][All Lists]

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

RE: Nonstandard lib location & LD_RUN_PATH

From: David Masterson
Subject: RE: Nonstandard lib location & LD_RUN_PATH
Date: Tue, 29 Nov 2005 12:20:08 -0800

Jason Martin wrote:
> LD_LIBRARY_PATH only affects runtime; since I can't set that
> value on all the clients, I instead need to have the binary look
> in the correct location inherently.
> -Jason Martin
> On Mon, Nov 28, 2005 at 08:17:32PM -0800, Brian C. Hill wrote:
>>      LD_RUN_PATH works for at least both Linux and SunOS 5 (Solaris 2),
>> since -R<path> isn't a Linux ld directive.
>> Brian
>> ======================================================================
>> On Mon, Nov 28, 2005 at 05:01:38PM -0800, David Masterson wrote:
>>> It would seem that the most crossplatform standard way would be to
>>> set LD_LIBRARY_PATH in during the processing to search
>>> for the BerkeleyDB library.

But the problem you're running into is during the "configure" of cfengine, so
what does it matter if the *test* executable that 'configure' generates has
the correct location internally or picks it up properly at runtime?  The
problem appears to be that not all compilers have an option to pass the path
properly to the linker the path to put into the executable.  From experience,
LD_LIBRARY_PATH seems the most universal way (but I could be wrong).

David Masterson
VMware, Inc.
Palo Alto, CA

reply via email to

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