Date: Thu, 11 Nov 1999 17:34:23 -0800 (PST) From: Mike Meyer <mwm@phone.net> To: stable@freebsd.org Subject: Re: ldconfig finding libraries, but ld is not. Message-ID: <14379.28319.927705.778764@guru.phone.net> In-Reply-To: <19991111144938.B69565@pinky.plambert.net> References: <14378.28246.28493.440833@guru.phone.net> <199911112213.RAA34417@server.baldwin.cx> <14379.17630.340446.163663@guru.phone.net> <19991111144938.B69565@pinky.plambert.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Paul M . Lambert writes: ;->It seems reasonable that /usr/local/lib doesn't get special treatment, ;->since it doesn't _need_ to have special treatment for everyone. Except, of course, that /usr/local/lib *does* get special treatment! It's listed in ldconfig_paths (and the aout subdir ldconfig_paths_aout), along with /usr/X11R6/lib & /usr/lib/compat. None of those are part of the OS, though all are part of the distribution. This seems a tad inconsistent. We make sure that the person installing software doesn't have to do anything extra to make it work at the install time - but someone trying to compile against them is left out in the code because "they aren't part of the OS". <mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14379.28319.927705.778764>