Re: [PLUG] Testing a new glibc

[gabriel rosenkoetter <gr@eclipsed.net>]

On Tue, Feb 18, 2003 at 09:53:34PM -0500, gabriel rosenkoetter wrote:
> Setting LDFLAGS=-Wl,--rpath -Wl,/usr/local/glibc-3.2/lib and
> CPPFLAGS=-I/usr/local/glibc-3.2/include ought to do it.

Alternatively, you could set:

  LD_RUN_PATH=/usr/local/glibc-3.2/lib:<your normal lib path>

during LINKING (note that doing this means you DON'T have to set
LD_LIBRARY_PATH at runtime... this is a CORRECT use of the LD_*
variables).

Alternatively, to test already-built binaries which link against
glibc (to test portability and know that you don't have to rebuild
the world), set LD_LIBRARY_PATH=<yadda>. This is also a correct use
of the LD_* variables.

I stress the correctness here because they are so frequently abused.
If a vendor tells you you need to set LD_LIBRARY_PATH, they don't
know what the hell they're doing. (Note that both Oracle and
ColdFusion include the setting of LD_LIBRARY_PATH, and suggest you
do so in /etc/profile... morons.)

-- 
gabriel rosenkoetter
gr@eclipsed.net

Attachment: pgpuo6eYpn0R9.pgp
Description: PGP signature