linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Kevin B. Hendricks" <kevin.hendricks@sympatico.ca>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: can/should we use gcc 3.1 to compile kernels
Date: Fri, 7 Jun 2002 15:44:56 -0400	[thread overview]
Message-ID: <200206071544.56448.kevin.hendricks@sympatico.ca> (raw)
In-Reply-To: <20020607193833.GO14252@opus.bloom.county>


Hi,

Not too bad warnings-wize excpet for the controlfb.c where it constanly
gave a funny warning about "pasting ->".

It did this for every occurence of the macro CNTRL_REG which I must admit
has two ## which I think gcc was misinterpreting somehow.


Other than that just the occaissioanal wanring about unused variables and
things like that.

I should have saved the build.log

I hate mixing compilers.  I have moved my system to gcc 3.1 from Franz but
I would like to keep gcc 2.95.4 in /usr/local/ or some other place just in
case I ever need it for things like glibc and the kernel.

Thanks,

Kevin

On June 7, 2002 03:38, Tom Rini wrote:
> 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.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-06-07 19:44 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
2002-06-07 19:44   ` Kevin B. Hendricks [this message]
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=200206071544.56448.kevin.hendricks@sympatico.ca \
    --to=kevin.hendricks@sympatico.ca \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=trini@kernel.crashing.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 NNTP newsgroup(s).