Date: Wed, 2 Sep 1998 18:13:42 -0500 (CDT) From: Joel Ray Holveck <joelh@gnu.org> To: jdp@polstra.com Cc: taob@risc.org, current@FreeBSD.ORG Subject: Re: Why no ldconfig for ELF? Message-ID: <199809022313.SAA09819@detlev.UUCP> In-Reply-To: <199809021600.JAA22787@austin.polstra.com> (message from John Polstra on Wed, 02 Sep 1998 09:00:59 -0700) References: <Pine.GSO.3.96.980902111219.689F-100000@tor-dev1.nbc.netcom.ca> <199809021600.JAA22787@austin.polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> 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. How is this a win? Say I'm taking a binary from somebody who installed libXpm in /usr/X11R6/lib, and didn't have a /usr/local/lib, which is where my libXpm resides. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped 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?199809022313.SAA09819>