From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: Andreas Schwab <schwab@suse.de>
Cc: Richard Henderson <rth@redhat.com>,
Zack Weinberg <zack@codesourcery.com>,
Andrew Pinski <pinskia@physics.uc.edu>,
gcc@gcc.gnu.org, rth@gcc.gnu.org
Subject: Re: Mainline bootstrap failure in toplev.c
Date: Wed, 01 Dec 2004 21:46:00 -0000 [thread overview]
Message-ID: <200412011546.39505.bangerth@ices.utexas.edu> (raw)
In-Reply-To: <jeeki98zxn.fsf@sykes.suse.de>
> There was never any use of __KERNEL__ in linux/compile-gcc+.h in any
> released version of the kernel sources. Looks like a bug specific to
> Mandrake.
OK, good to know. I'll see whether I can find a place to report bugs with
mandrake...
W.
-------------------------------------------------------------------------
Wolfgang Bangerth email: bangerth@ices.utexas.edu
www: http://www.ices.utexas.edu/~bangerth/
next prev parent reply other threads:[~2004-12-01 21:46 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
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 [this message]
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=200412011546.39505.bangerth@ices.utexas.edu \
--to=bangerth@ices.utexas.edu \
--cc=gcc@gcc.gnu.org \
--cc=pinskia@physics.uc.edu \
--cc=rth@gcc.gnu.org \
--cc=rth@redhat.com \
--cc=schwab@suse.de \
--cc=zack@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).