Date: Wed, 2 Sep 1998 19:14:14 +0200 (CEST) From: Mikael Karpberg <karpen@ocean.campus.luth.se> To: jdp@polstra.com (John Polstra) Cc: current@FreeBSD.ORG Subject: Re: Why no ldconfig for ELF? Message-ID: <199809021714.TAA11179@ocean.campus.luth.se> In-Reply-To: <199809021600.JAA22787@austin.polstra.com> from John Polstra at "Sep 2, 98 09:00:59 am"
next in thread | previous in thread | raw e-mail | index | archive | help
According to John Polstra: > In article <Pine.GSO.3.96.980902111219.689F-100000@tor-dev1.nbc.netcom.ca>, > Brian Tao <taob@risc.org> wrote: > > I've seen it mentioned dozens of times that ldconfig is deprecated > > with our move to ELF, but I don't think anyone explained why. How > > does ELF know where to find libraries then? Surely we don't have to > > depend on setting LD_LIBRARY_PATH to include /usr/X11R6/lib and > > /usr/local/lib and whatever other local library paths? Solaris > > requires this, and it's been a big pain in the rear. Besides, a > > globally-enforced library search path seems to be much more secure > > than allowing users to specify their own. > > 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??? If so, that seems like a giant step backwards, no? /Mikael 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?199809021714.TAA11179>