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
Date: Wed, 01 Dec 2004 18:03:00 -0000 [thread overview]
Message-ID: <20041201100303.A15210@synopsys.com> (raw)
In-Reply-To: <20041201175631.GB10397@nevyn.them.org>; from drow@false.org on Wed, Dec 01, 2004 at 12:56:31PM -0500
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.
next prev parent reply other threads:[~2004-12-01 18:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 15:32 Wolfgang Bangerth
2004-12-01 15:38 ` Andrew Pinski
2004-12-01 15:56 ` Wolfgang Bangerth
2004-12-01 17:09 ` Richard Henderson
2004-12-01 17:18 ` Wolfgang Bangerth
2004-12-01 17:20 ` Richard Henderson
2004-12-01 17:38 ` Joe Buck
2004-12-01 17:51 ` Paul Brook
2004-12-01 17:55 ` Joe Buck
2004-12-01 17:56 ` Daniel Jacobowitz
2004-12-01 18:03 ` Joe Buck [this message]
2004-12-01 18:05 ` Daniel Jacobowitz
2004-12-01 17:56 ` Daniel Jacobowitz
2004-12-01 18:35 ` Richard Henderson
2004-12-01 17:49 ` Zack Weinberg
2004-12-01 20:12 ` Wolfgang Bangerth
2004-12-01 20:39 ` Richard Henderson
2004-12-01 21:15 ` Wolfgang Bangerth
2004-12-01 21:28 ` Andreas Schwab
2004-12-01 21:32 ` Wolfgang Bangerth
2004-12-01 21:35 ` Andreas Schwab
2004-12-01 21:46 ` Wolfgang Bangerth
2004-12-01 17:50 ` Wolfgang Bangerth
2004-12-02 8:23 ` Kai Henningsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041201100303.A15210@synopsys.com \
--to=joe.buck@synopsys.com \
--cc=gcc@gcc.gnu.org \
--cc=paul@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).