RE: Nonstandard lib location & LD_RUN_PATH

[Martin, Jason H]

Presumably the problem that causes the test executable to fail will also
cause the final 'cfagent' executable to fail.  I ran across an
interesting articule about the merits of using LD_LIBRARY_PATH:
http://www.visi.com/~barr/ldpath.html

-Jason Martin

> -----Original Message-----
> From: 
> help-cfengine-bounces+jason.h.martin=cingular.com@gnu.org 
> [mailto:help-cfengine-bounces+jason.h.martin=cingular.com@gnu.
> org] On Behalf Of David Masterson
> Sent: Tuesday, November 29, 2005 12:20 PM
> To: Jason Martin; help-cfengine@gnu.org
> Subject: RE: Nonstandard lib location & LD_RUN_PATH
> 
> 
> 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 configure.ac 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
> 
> 
> _______________________________________________
> Help-cfengine mailing list
> Help-cfengine@gnu.org 
> http://lists.gnu.org/mailman/listinfo/help-> cfengine
>