From: Reichelt <reichelt@igpm.rwth-aachen.de>
To: gcc@gcc.gnu.org
Subject: Re: compiling linux kernels with GCC 3.0
Date: Wed, 10 Oct 2001 11:23:00 -0000 [thread overview]
Message-ID: <200110101830.UAA04459@numa6.igpm.rwth-aachen.de> (raw)
In article < http://gcc.gnu.org/ml/gcc/2001-10/msg00666.html > Linus
Torvalds writes:
> gcc-3.0.x is supposed to work fine. It's not the recommended compiler
> for "regular users", but that's not due to known problems, but simply
> due to lack of history with it. I know several developers who are
using
> current gcc snapshots for kernel compiles, and they have yet to report
> compiler trouble. (Well, I've actually gotten one report of kernel
> trouble, but that was from rth with his personal gcc sandbox, and he
> seemed to fix that ;)
gcc is having problems with the ISDN subsystem of recent kernels:
The file capi.c won't compile with 3.0.x, see PR 4298 :-(
However, you can compile it, if you use "-O1" instead of "-O2" :-)
Greetings,
Volker Reichelt
next reply other threads:[~2001-10-10 11:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 11:23 Reichelt [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-10 5:37 Alan Lehotsky
2001-10-10 7:22 ` Florian Weimer
2001-10-10 9:04 ` Josh McKinney
2001-10-10 9:26 ` Linus Torvalds
2001-10-10 11:09 ` Joe Buck
2001-10-10 11:23 ` Linus Torvalds
2001-10-10 15:23 ` Joe Buck
2001-10-10 16:19 ` Paolo Carlini
2001-10-10 16:58 ` Richard Henderson
2001-10-10 17:09 ` Paolo Carlini
2001-10-10 17:12 ` Richard Henderson
2001-10-10 19:03 ` Tim Prince
2001-10-10 15:39 ` Matthew Woodcraft
2001-10-10 11:40 ` Mark Mitchell
2001-10-10 14:01 ` Paolo Carlini
2001-10-10 14:15 ` Mark Mitchell
2001-10-10 14:54 ` Paolo Carlini
2001-10-10 15:57 ` Joe Buck
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=200110101830.UAA04459@numa6.igpm.rwth-aachen.de \
--to=reichelt@igpm.rwth-aachen.de \
--cc=gcc@gcc.gnu.org \
/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).