Mainline bootstrap failure in toplev.c

[Daniel Jacobowitz]

On Wed, Dec 01, 2004 at 09:55:32AM -0800, Joe Buck wrote:
> On Wed, Dec 01, 2004 at 05:51:19PM +0000, Paul Brook wrote:
> > On Wednesday 01 December 2004 17:38, Joe Buck wrote:
> > > On Wed, Dec 01, 2004 at 09:20:09AM -0800, Richard Henderson wrote:
> > > > On Wed, Dec 01, 2004 at 11:18:21AM -0600, Wolfgang Bangerth wrote:
> > > > > The question remains as to what to do on systems with headers that
> > > > > some people describe with words I dare not repeat here?
> > > >
> > > > Fixinclude them.
> > >
> > > We will then get angry e-mails from Mr. Torvalds and friends, since if
> > > the headers are fixincluded, future kernel builds won't see them.
> > > Of course, they can use explicit -I directives to get the non-modified
> > > headers.
> > 
> > I'd expect kernel builds should be using their own headers, not the installed 
> > system ones.
> 
> But this *is* one of "their own headers".  The bug is that, on most
> GNU/Linux systems, kernel headers are included by some of the headers in
> /usr/include.

This is a _copy_ of those files, provided by the distributor, living in
/usr/include.  The kernel will not reference them during build.

-- 
Daniel Jacobowitz