Date: Sat, 07 Jul 2012 01:31:57 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Dimitry Andric <dimitry@andric.com> Cc: toolchain@FreeBSD.org, David Chisnall <theraven@FreeBSD.org> Subject: Re: gcc46 header search path Message-ID: <4FF7675D.9090609@FreeBSD.org> In-Reply-To: <4FF75C5E.3020105@andric.com> 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> <714BF622-A1B3-4A4A-A8BC-DCA82B4434A2@FreeBSD.org> <E3F8219C-EF7F-4AB5-A00B-5BD251ECEFFE@bsdimp.com> <4FF75C5E.3020105@andric.com>
next in thread | previous in thread | raw e-mail | index | archive | help
on 07/07/2012 00:45 Dimitry Andric said the following: > On 2012-07-06 22:44, Warner Losh wrote: > ... >> The reasons are that /usr/local/include superceds anything in /usr/include. This is dangerous. Users should get just the system default libraries and headers when they compile unless they ask for more. That's what makes it stupid. > > Well, one issue is that it becomes tricky to *remove* /usr/local/include > from the include path, if you so desire, since it's built-in... Unless > you start fiddling with -nostdinc, but that is rather painful. > My opinion is that system builds (buildworld, buildkernel) must use -nostdinc. Other types of build should accept the state of matters. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FF7675D.9090609>