From: Alessandro Suardi <alessandro.suardi@oracle.com>
To: Josh McKinney <forming@home.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: compiling kernel with gcc-3 (was: 2.4.10-pre5)
Date: Sun, 09 Sep 2001 23:22:04 +0200 [thread overview]
Message-ID: <3B9BDD7C.78B58344@oracle.com> (raw)
In-Reply-To: <E15fhnT-0003np-00@the-village.bc.nu> <3B9A95C7.DDF81890@oracle.com> <20010908230539.A4927@home.com>
Josh McKinney wrote:
>
> Since I have gotten a decent amount of flame mail from my one-liner posted
> yesterday, I am just curious. Has anyone really been able to successfully
> compile their kernel with gcc-3*. I did once or twice long before it was
> released, but it dies on the same error everytime. I posted it to the
> GCC mailing list because it was an internal compiler error, but it went
> unanswered, along with other reports of the same bug. Anyway, I just want
> to see if someone really is able to use it as a reliable compiler.
>
I've been compiling kernels since June 22 with 3.0, never a
problem. -pre5 and -pre6 compiled with 3.0.1 backing out the
rd.c changes.
--alessandro
"this is no time to get cute, it's a mad dog's promenade
so walk tall, or baby don't walk at all"
(Bruce Springsteen, 'New York City Serenade')
next prev parent reply other threads:[~2001-09-09 21:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-08 5:12 2.4.10-pre5 Garst R. Reese
2001-09-08 6:14 ` 2.4.10-pre5 Kingsley Foreman
2001-09-08 6:46 ` 2.4.10-pre5 Josh McKinney
2001-09-08 8:19 ` 2.4.10-pre5 Nicholas Knight
2001-09-08 9:32 ` 2.4.10-pre5 Eyal Lebedinsky
2001-09-08 13:05 ` 2.4.10-pre5 Alan Cox
2001-09-08 22:03 ` 2.4.10-pre5 Alessandro Suardi
2001-09-09 4:05 ` 2.4.10-pre5 Josh McKinney
2001-09-09 4:14 ` 2.4.10-pre5 Steven Walter
2001-09-09 11:48 ` 2.4.10-pre5 (and gcc-3) Ken Moffat
2001-09-09 21:22 ` Alessandro Suardi [this message]
2001-09-08 10:36 ` 2.4.10-pre5 Peter Osterlund
2001-09-08 12:57 ` 2.4.10-pre5 Garst R. Reese
2001-09-09 5:30 ` 2.4.10-pre5/pre6 Garst R. Reese
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=3B9BDD7C.78B58344@oracle.com \
--to=alessandro.suardi@oracle.com \
--cc=forming@home.com \
--cc=linux-kernel@vger.kernel.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