All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tobias Klauser <tklauser@nuerscht.ch>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] janitor project: fix gcc 4 warnings
Date: Sun, 19 Dec 2004 21:00:38 +0000	[thread overview]
Message-ID: <200412192200.44211.tklauser@nuerscht.ch> (raw)
In-Reply-To: <20041219190903.GA30192@muc.de>


[-- Attachment #1.1: Type: text/plain, Size: 1271 bytes --]

Hi

On Sunday 19 December 2004 20:09, Andi Kleen wrote:
> Short howto:
>
> Get
> ftp://gcc.gnu.org/pub/gcc/snapshots/4.0-20041219/gcc-core-4.0-20041219.tar.
>bz2
>
> Untar it and compile with
>
> mkdir obj
> ../gcc-*/configure --disable-checking --enable-languages=c
> --prefix=/usr/local/gcc4 make bootstrap
> <as root>
> make install
>
>
> Then compile an uptodate 2.6 kernel with:
>
> make allmodconfig
> make CC=/usr/local/gcc4/bin/gcc 2>&1 | tee LOG
> grep warning LOG
Cool howto, thanks. Maybe that should go onto the TODO list over at 
kerneljanitors.org?

>
> You'll see lots of warnings in LOG. Fix them all and submit patches
> through the usual janitor channels.

I already compiled GCC4 and it took about 15 minutes on an Athlon Tbird 1.4 
GHz to finish. When compiling Linux 2.6.10-rc3 with GCC4 there are lots of 
warnings (as expected) and even a fatal error.
So I'm trying to fix some of these warnings. They are all over the kernel tree 
and so I'm curious what would be the best method to split and submit the 
patches?

Thanks, Tobias

-- 
Tobias Klauser <tklauser@nuerscht.ch>

GPG-Key 0x3A445520 http://tklauser.politux.org/tklauser.asc
    Fingerprint = 7474 D486 E4FC 5113 561D  B1E3 72BC 0E7E 3A44 5520

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 167 bytes --]

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors

  parent reply	other threads:[~2004-12-19 21:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-19 19:09 [KJ] janitor project: fix gcc 4 warnings Andi Kleen
2004-12-19 19:47 ` Matthew Wilcox
2004-12-19 20:03 ` Andi Kleen
2004-12-19 21:00 ` Tobias Klauser [this message]
2004-12-20  0:13 ` Adrian Bunk
2004-12-20  7:10 ` Andi Kleen
2004-12-20  8:03 ` Andi Kleen
2004-12-20  8:04 ` Andi Kleen
2004-12-20 12:31 ` Arnd Bergmann
2004-12-22 16:44 ` Kovarththanan Rajaratnam
2005-02-07 23:14 ` Randy.Dunlap
2007-02-15 19:34 ` devzero

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=200412192200.44211.tklauser@nuerscht.ch \
    --to=tklauser@nuerscht.ch \
    --cc=kernel-janitors@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 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.