From owner-freebsd-arch Fri Nov 12 2:55:54 1999 Delivered-To: freebsd-arch@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 7AD6214C05 for ; Fri, 12 Nov 1999 02:55:51 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id LAA14252 for ; Fri, 12 Nov 1999 11:55:50 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id LAA26011 for freebsd-arch@freebsd.org; Fri, 12 Nov 1999 11:55:50 +0100 (MET) Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id BC1E414C05 for ; Fri, 12 Nov 1999 02:55:39 -0800 (PST) (envelope-from freebsd-arch@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id LAA39347 for arch@FreeBSD.org; Fri, 12 Nov 1999 11:26:42 +0100 (CET) (envelope-from freebsd-arch@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for arch@FreeBSD.org (arch@FreeBSD.org) To: arch@freebsd.org Date: Fri, 12 Nov 1999 11:26:35 +0100 From: Marcel Moolenaar Message-ID: <382BEB5B.EDE3FFC3@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: Subject: Re: /usr/local Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > > How would people feel about adding /usr/local/include and > /usr/local/lib to gcc's default header and library search paths, > respectively? As somebody pointed out in a recent thread on -stable, > we already have /usr/local/lib in the default ldconfig_path, so why > not in the link-time search path as well? It can be dangerous. Sometimes people have headers in /usr/local/include that conflict with headers in /usr/include. If /usr/local/include is added as default search path, make world could break. The evidence can be found in spurious postings about some port breakage (rpm for example). Also, having /usr/local/lib in ldconfig_path is not really a precedent for adding /usr/local/include and /usr/local/lib to the standard compile-time search paths. We need (for example) /usr/X11R6/lib in ldconfig_path, but don't want X11 related searches baked into our compiler. If we do it, then it should be done with care. Personally, I don't think it's really necessary... -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message