From: Tom Rini <trini@kernel.crashing.org>
To: "Kevin B. Hendricks" <kevin.hendricks@sympatico.ca>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: can/should we use gcc 3.1 to compile kernels
Date: Fri, 7 Jun 2002 12:38:33 -0700 [thread overview]
Message-ID: <20020607193833.GO14252@opus.bloom.county> (raw)
In-Reply-To: <200206081337.31359.kevin.hendricks@sympatico.ca>
On Sat, Jun 08, 2002 at 01:41:12PM -0400, Kevin B. Hendricks wrote:
> Has anyone successfully used gcc 3.1 or gcc 3.1.1-pre to build actual
> working kernels and tested them?
>
> Does it work?
There's at least a few people who've done it. Personally I'll be using
2.95.3 (or 2.95 from CVS) until forced to do otherwise, just because
it's the most well-tested compiler.
That said, if you do use 3.1, you'll get a bunch more warnings which I
don't think you can turn off, which has kind of annoyed some developers.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-07 19:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-08 17:41 can/should we use gcc 3.1 to compile kernels Kevin B. Hendricks
2002-06-07 18:31 ` Kaoru Fukui
2002-06-07 19:38 ` Tom Rini [this message]
2002-06-07 19:44 ` Kevin B. Hendricks
2002-06-07 20:19 ` Tom Rini
2002-06-07 20:36 ` Franz Sirl
2002-06-07 20:45 ` Tom Rini
2002-06-07 20:58 ` Franz Sirl
2002-06-07 23:39 ` Kevin B. Hendricks
2002-06-07 23:59 ` Tom Rini
2002-06-07 20:44 ` Kevin B. Hendricks
2002-06-07 20:50 ` Franz Sirl
2002-06-07 21:06 ` Kevin B. Hendricks
2002-06-07 21:40 ` Kaoru Fukui
2002-06-07 21:11 ` More GCC 3.1 Qs Conn Clark
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=20020607193833.GO14252@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=kevin.hendricks@sympatico.ca \
--cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.