From owner-freebsd-current Wed Sep 2 09:02:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA12661 for freebsd-current-outgoing; Wed, 2 Sep 1998 09:02:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12641 for ; Wed, 2 Sep 1998 09:02:15 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id JAA22787; Wed, 2 Sep 1998 09:00:59 -0700 (PDT) (envelope-from jdp) Message-Id: <199809021600.JAA22787@austin.polstra.com> To: taob@risc.org Subject: Re: Why no ldconfig for ELF? In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Wed, 02 Sep 1998 09:00:59 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Brian Tao 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. -- 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