Date: Fri, 6 Jul 2012 20:11:40 +0100 From: David Chisnall <theraven@FreeBSD.org> To: Andriy Gapon <avg@FreeBSD.org> Cc: toolchain@FreeBSD.org Subject: Re: gcc46 header search path Message-ID: <714BF622-A1B3-4A4A-A8BC-DCA82B4434A2@FreeBSD.org> In-Reply-To: <4FF7182A.9070803@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>
next in thread | previous in thread | raw e-mail | index | archive | help
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=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?714BF622-A1B3-4A4A-A8BC-DCA82B4434A2>