From: ahoward <ahoward@...>
Date: 2002-11-13T02:50:14+09:00
Subject: Re: setting LD_LIBRARY_PATH doesn't seem to work?

On Wed, 13 Nov 2002, Michael Campbell wrote:

> > why not compile the module using LD_RUN_PATH?  relying on
> > LD_LIBRARY_PATH is
> > evil ;-)
>
> I've heard this charge levied before; can someone tell me the
> inherent evil in it?
>
> I'm not doubting anyone, just curious.

this sums it up

  http://www.visi.com/~barr/ldpath.html

mkmf uses LD_RUN_PATH to avoid these problems.  it sets LDSHARED to be
something like 'env LD_RUN_PATH=/usr/local/somepkg/lib gcc -shared' to avoid
the exact problem described earlier in this thread - which is requiring the
user/program to manage it's own binary dependancies.  i think of it like
having instance variable associate with an object : when the search path is
encoded in a shared library that 'object' knows it's own depends.  it does not
rely on user code to manage them.

-a

>
>
>
> =====
> --
>
> Yahoo IM: michael_s_campbell
>
> __________________________________________________
> Do you Yahoo!?
> U2 on LAUNCH - Exclusive greatest hits videos
> http://launch.yahoo.com/u2
>
>

-- 

 ====================================
 | Ara Howard
 | NOAA Forecast Systems Laboratory
 | Information and Technology Services
 | Data Systems Group
 | R/FST 325 Broadway
 | Boulder, CO 80305-3328
 | Email: ahoward@fsl.noaa.gov
 | Phone:  303-497-7238
 | Fax:    303-497-7259
 ====================================