From owner-freebsd-toolchain@FreeBSD.ORG Fri Jul 6 19:11:44 2012 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 53C1A1065673; Fri, 6 Jul 2012 19:11:44 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) by mx1.freebsd.org (Postfix) with ESMTP id 1D4408FC14; Fri, 6 Jul 2012 19:11:44 +0000 (UTC) Received: from c120.sec.cl.cam.ac.uk (c120.sec.cl.cam.ac.uk [128.232.18.120]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id q66JBfUn033202 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Fri, 6 Jul 2012 19:11:42 GMT (envelope-from theraven@FreeBSD.org) Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=us-ascii From: David Chisnall In-Reply-To: <4FF7182A.9070803@FreeBSD.org> Date: Fri, 6 Jul 2012 20:11:40 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <714BF622-A1B3-4A4A-A8BC-DCA82B4434A2@FreeBSD.org> References: <4FF60A9E.5070503@FreeBSD.org> <4FF6DB51.40904@FreeBSD.org> <508B8B4E-DF5E-412B-BD2B-86F21EBF4C8C@bsdimp.com> <4FF700CF.2000206@FreeBSD.org> <1DED79CC-CACD-4D22-9F1F-E3EB17938EB6@bsdimp.com> <4FF7182A.9070803@FreeBSD.org> To: Andriy Gapon X-Mailer: Apple Mail (2.1278) Cc: toolchain@FreeBSD.org Subject: Re: gcc46 header search path X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jul 2012 19:11:44 -0000 On 6 Jul 2012, at 17:54, Andriy Gapon wrote: > Yeah. Honestly speaking I myself was not aware of what is written in = that link > and I thought that our gcc ports (from ports) added /usr/local/include = to the > default search path by some mistake. And if somebody asked me what I = thought > about the idea of adding /usr/local/include to the default path, I'd = say that it > was a stupid idea. Why? The number one question I get from developers new FreeBSD is 'I = wanted to use libfoo from ports, I stalled it, and now [gcc,clang] = doesn't find the headers, why not?' No one has yet provided me with a = sane reason why our system compiler would not look in the standard = locations where we install headers and libraries. Running configure = scripts on FreeBSD is a colossal pain because of this - you often need = to explicitly say -with-foo-include=3D/usr/local/include = -with-foo-lib=3D/usr/local/lib for an arbitrary number of values of foo, = depending on the library. Please, please, please, can we put our standard library and header paths = in the compiler standard header or library paths, or can someone give me = a good reason other than 'it's a stupid idea' why we should force every = single program that anyone compiles on FreeBSD to do = CFLAGS=3D-I/usr/local/include LDFLAGS=3D-L/usr/local/lib? David=