From owner-freebsd-stable Thu Nov 11 20:17:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ns.itga.com.au (ns.itga.com.au [192.83.119.129]) by hub.freebsd.org (Postfix) with ESMTP id E822415425 for ; Thu, 11 Nov 1999 20:17:04 -0800 (PST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by ns.itga.com.au (8.9.3/8.9.3) with ESMTP id PAA98567; Fri, 12 Nov 1999 15:16:54 +1100 (EST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id PAA29570; Fri, 12 Nov 1999 15:16:54 +1100 (EST) Message-Id: <199911120416.PAA29570@lightning.itga.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: Mike Meyer Cc: stable@FreeBSD.ORG Subject: Re: ldconfig finding libraries, but ld is not. In-reply-to: Your message of Thu, 11 Nov 1999 16:33:51 -0800. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Nov 1999 15:16:53 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yeah, I did that. /usr/local is on /usr, and /home has stuff that's > local on it. It's just a minor annoyance (as opposed to, say, Windows > UI behavior, which is a major annoyance). This is an old, old, _OLD_ problem. I personally have been dealing with it since the days of mod.sources. I even remember the wrenching sensation that came from discovering that there were these very substantial, useful programs out there and people _just gave them away_. The mind boggled. For many years we have (on our Sun systems) had a /usr/local/{bin,lib,sbin,etc} hierarchy for stuff from the net (etc) that isn't part of the OS, and /usr/ local//{bin,lib,etc} for locally-developed stuff. It's a 3-way distinction that has proved very useful. It does still annoy me that gcc on Suns will look in /usr/local/include but the linker won't look in /usr/local/lib... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message