Date: Sun, 14 Jun 2009 18:29:56 -0700 From: Marcel Moolenaar <xcllnt@mac.com> To: Mark Murray <markm@FreeBSD.org> Cc: "current@freebsd.org" <current@freebsd.org> Subject: Re: Build is polluted by host build environment. Message-ID: <FD89B7D3-AA99-4C3E-8EFF-D9CA03840F5D@mac.com> In-Reply-To: <E1MFkyG-000IUX-Ia@greatest.grondar.org> References: <E1MFX3z-000HWl-TK@greatest.grondar.org> <C800F72C-D396-42AE-AAEF-7C12ED34DA10@mac.com> <E1MFXuj-000Hb7-U2@greatest.grondar.org> <1464A93A-D187-476F-A143-E37EB6BB01EF@mac.com> <E1MFkyG-000IUX-Ia@greatest.grondar.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 14, 2009, at 1:21 AM, Mark Murray wrote: > Marcel Moolenaar writes: >> cc_tools is supposed to use /usr/include when it's building the cross >> tools, so your email does not demonstrate a problem per se. > > I said in the original email that the building was fine for all the > tools stuff, and that the failure occurred once the "real" build got > under way. Ok. But still, cc_tools builds programs that run on the host and as such *must* use headers in /usr/include. The GCC build is too convoluted to state that the observed breakage is a problem or that it isn't a problem without detailed analysis of what was being built and how it's used. > If you look at the patch I supplied, you'll see that I only break > /usr/include once the tools are done. Unfortunately that is not exactly true. > Having done that, the real build proceeds, and breaks in cc_tools for > the reason stated. Full build log available on request. Please make the full logs available somewhere. -- Marcel Moolenaar xcllnt@mac.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FD89B7D3-AA99-4C3E-8EFF-D9CA03840F5D>