This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Mainline bootstrap failure in toplev.c

From: Joe Buck <Joe dot Buck at synopsys dot COM>
To: Richard Henderson <rth at redhat dot com>,Wolfgang Bangerth <bangerth at ices dot utexas dot edu>,Andrew Pinski <pinskia at physics dot uc dot edu>, gcc at gcc dot gnu dot org,rth at gcc dot gnu dot org
Date: Wed, 1 Dec 2004 09:38:15 -0800
Subject: Re: Mainline bootstrap failure in toplev.c
References: <200412010932.02561.bangerth@ices.utexas.edu> <200412010955.59087.bangerth@ices.utexas.edu> <20041201170931.GA12839@redhat.com> <200412011118.21662.bangerth@ices.utexas.edu> <20041201172009.GC12839@redhat.com>

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.

Follow-Ups:
- Re: Mainline bootstrap failure in toplev.c
  - From: Paul Brook
- Re: Mainline bootstrap failure in toplev.c
  - From: Richard Henderson

References:
- Mainline bootstrap failure in toplev.c
  - From: Wolfgang Bangerth
- Re: Mainline bootstrap failure in toplev.c
  - From: Wolfgang Bangerth
- Re: Mainline bootstrap failure in toplev.c
  - From: Richard Henderson
- Re: Mainline bootstrap failure in toplev.c
  - From: Wolfgang Bangerth
- Re: Mainline bootstrap failure in toplev.c
  - From: Richard Henderson

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]