From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-106110-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 23673 invoked by alias); 1 Dec 2004 18:03:20 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 23592 invoked from network); 1 Dec 2004 18:03:05 -0000
Received: from unknown (HELO boden.synopsys.com) (198.182.44.79)
  by sourceware.org with SMTP; 1 Dec 2004 18:03:05 -0000
Received: from maiden.synopsys.com (maiden.synopsys.com [146.225.100.170])
	by boden.synopsys.com (Postfix) with ESMTP
	id 2A737DEA8; Wed,  1 Dec 2004 10:02:29 -0800 (PST)
Received: from piper.synopsys.com (localhost [127.0.0.1])
	by maiden.synopsys.com (8.9.1/8.9.1) with ESMTP id KAA27397;
	Wed, 1 Dec 2004 10:03:04 -0800 (PST)
Received: (from jbuck@localhost)
	by piper.synopsys.com (8.11.6/8.11.6) id iB1I33515553;
	Wed, 1 Dec 2004 10:03:03 -0800
X-Authentication-Warning: piper.synopsys.com: jbuck set sender to Joe.Buck@synopsys.com using -f
Date: Wed, 01 Dec 2004 18:03:00 -0000
From: Joe Buck <Joe.Buck@synopsys.COM>
To: Paul Brook <paul@codesourcery.com>, gcc@gcc.gnu.org
Subject: Re: Mainline bootstrap failure in toplev.c
Message-ID: <20041201100303.A15210@synopsys.com>
References: <200412010932.02561.bangerth@ices.utexas.edu> <20041201172009.GC12839@redhat.com> <20041201093815.A12025@synopsys.com> <200412011751.19312.paul@codesourcery.com> <20041201095532.A14487@synopsys.com> <20041201175631.GB10397@nevyn.them.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20041201175631.GB10397@nevyn.them.org>; from drow@false.org on Wed, Dec 01, 2004 at 12:56:31PM -0500
X-SW-Source: 2004-12/txt/msg00072.txt.bz2

On Wed, Dec 01, 2004 at 12:56:31PM -0500, Daniel Jacobowitz wrote:
> On Wed, Dec 01, 2004 at 09:55:32AM -0800, Joe Buck wrote:
> > 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.

Then this is bug in the distro; it changes the meaning of
"inline" for any program that inadvertently includes that copied header.
In this case, a fixincludes approach is harmless, as long as kernel
compiles never use the copy.