From: Matthias Andree <matthias.andree@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Compiling kernel with SuSE 8.2/gcc 3.3
Date: Wed, 11 Jun 2003 13:28:59 +0200 [thread overview]
Message-ID: <20030611112859.GA9031@merlin.emma.line.org> (raw)
In-Reply-To: <3EE6B7A2.3000606@austin.rr.com>
On Wed, 11 Jun 2003, Steve French wrote:
> Stephan von Krawczynski <skraw@ithnet.com> writes:
>
> >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
>
> I also noticed lots of compiler warnings with gcc 3.3, now default in SuSE,
> and cleaned up most of them for the cifs vfs but there are a few that just
> look wrong for gcc to spit out warnings on. For example the following
> local variable definition and the similar ones in the same file
> (fs/cifs/inode.c):
Did you try with a release version of gcc 3.3? The one shipped on SuSE
Linux 8.2 media/FTP is a pre-release version.
(If SuSE would only ship patch-level updates to such essential
components, say, 3.2.2 for 8.1 and the released 3.3 for 8.2.)
--
Matthias Andree
next prev parent reply other threads:[~2003-06-11 11:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2003-06-11 16:12 ` Andreas Schwab
[not found] <3EE6B7A2.3000606@austin.rr.com.suse.lists.linux.kernel>
2003-06-11 8:01 ` 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
[not found] <20030408134240.45cdad7e.skraw@ithnet.com.suse.lists.linux.kernel>
2003-04-08 13:14 ` Andi Kleen
[not found] <20030408115008$0cd2@gated-at.bofh.it>
2003-04-08 12:02 ` Arnd Bergmann
-- 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=20030611112859.GA9031@merlin.emma.line.org \
--to=matthias.andree@gmx.de \
--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
all inboxes | Powered by JetHome®