Date: Wed, 02 Sep 1998 10:50:07 -0700 From: John Polstra <jdp@polstra.com> To: Mikael Karpberg <karpen@ocean.campus.luth.se> Cc: current@FreeBSD.ORG Subject: Re: Why no ldconfig for ELF? Message-ID: <199809021750.KAA23591@austin.polstra.com> In-Reply-To: Your message of "Wed, 02 Sep 1998 19:14:14 %2B0200." <199809021714.TAA11179@ocean.campus.luth.se>
next in thread | previous in thread | raw e-mail | index | archive | help
> > You specify the search path at _link_ time with LD_RUN_PATH or the > > "-R" linker option. The path is saved in the executable or shared > > library itself. > > Hmmm... What happens if I have a library in /usr/local/blah/lib/ and > link with that, and someone else has the library in /usr/local/lib/ > and he just FTPs my binary and runs it. Will it not run??? Correct. The recipient will either have to install the library in one of its standard places, or set LD_LIBRARY_PATH. Or, you will have to anticipate the possible places where he might decide to put the library, and code those into LD_RUN_PATH. > If so, that seems like a giant step backwards, no? It has already been discussed to death in the mailing lists. The goal of ELF is to have standard tools, not another set of deviant bastard children maintained by nobody. That means we do things the standard ELF way. It is easy to pick theoretical holes in anything new and different. I think once you've lived with it for a little while, you'll find that it's fine in practice. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809021750.KAA23591>