From: Arnd Bergmann <arnd@arndb.de>
To: Stephan von Krawczynski <skraw@ithnet.com>, linux-kernel@vger.kernel.org
Subject: Re: Compiling kernel with SuSE 8.2/gcc 3.3
Date: Tue, 08 Apr 2003 14:02:05 +0200 [thread overview]
Message-ID: <200304081202.h38C2Wgu010663@post.webmailer.de> (raw)
In-Reply-To: 20030408115008$0cd2@gated-at.bofh.it
Stephan von Krawczynski wrote:
> during tests with latest SuSE distro 8.2 compiling 2.4.21-pre6 showed a lot of
> "comparison between signed and unsigned" warnings. It looks like SuSE ships gcc
> 3.3 (prerelease). Is this compiler known to work for kernel compilation? Should
> therefore all these warnings be fixed?
We're building 2.4 and 2.5 kernels for s390 with a gcc-3.3 snapshot and we had to
fix a few places in the kernel source to make that work reliably. See
http://marc.theaimsgroup.com/?t=104611164800008&r=1&w=2 for more about this.
I have also tried using gcc-3.3 for building a 2.4 i386 kernel and needed a
small patch, but ymmv.
Arnd <><
next parent reply other threads:[~2003-04-08 11:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030408115008$0cd2@gated-at.bofh.it>
2003-04-08 12:02 ` Arnd Bergmann [this message]
[not found] <3EE6B7A2.3000606@austin.rr.com.suse.lists.linux.kernel>
2003-06-11 8:01 ` Compiling kernel with SuSE 8.2/gcc 3.3 Andi Kleen
2003-06-12 1:24 ` Steve French
2003-06-12 1:40 ` Andrew Morton
2003-06-12 2:17 ` Riley Williams
2003-06-12 2:00 ` Linus Torvalds
2003-06-12 12:52 ` Horst von Brand
2003-06-11 5:01 Steve French
2003-06-11 11:20 ` Richard B. Johnson
2003-06-11 13:59 ` Richard B. Johnson
2003-06-11 11:28 ` Matthias Andree
2003-06-11 16:12 ` Andreas Schwab
[not found] <20030408134240.45cdad7e.skraw@ithnet.com.suse.lists.linux.kernel>
2003-04-08 13:14 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2003-04-08 11:42 Stephan von Krawczynski
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=200304081202.h38C2Wgu010663@post.webmailer.de \
--to=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=skraw@ithnet.com \
/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