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 13:19:06 -0700 [thread overview]
Message-ID: <20020607201906.GP14252@opus.bloom.county> (raw)
In-Reply-To: <200206071544.56448.kevin.hendricks@sympatico.ca>
On Fri, Jun 07, 2002 at 03:44:56PM -0400, Kevin B. Hendricks wrote:
> Not too bad warnings-wize excpet for the controlfb.c where it constanly
> gave a funny warning about "pasting ->".
Sounds right. I think there was a few other things too..
> It did this for every occurence of the macro CNTRL_REG which I must admit
> has two ## which I think gcc was misinterpreting somehow.
Well, isn't:
#define x(foo) a_## foo ##_b
A semi-common thing, like we do in indirect_pci.c ? Or was it something
different?
> Other than that just the occaissioanal wanring about unused variables and
> things like that.
Lots of the USB stuff uses __FUNCTION__ which gcc-3.1 isn't happy
about.
> I should have saved the build.log
S'alright.
--
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 20:19 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
2002-06-07 20:19 ` Tom Rini [this message]
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=20020607201906.GP14252@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.