From: Domen Puncer <domen@coderock.org>
To: kernel-janitors@vger.kernel.org
Subject: [KJ] Re: janitor project: fix gcc 4 warnings
Date: Mon, 20 Dec 2004 13:02:38 +0000 [thread overview]
Message-ID: <20041220130238.GB29520@nd47.coderock.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]
On 19/12/04 22:00 +0100, Tobias Klauser wrote:
> 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?
Added.
>
> >
> > 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?
Patch per file (and per mail).
For submitting, Andrew's patch-bomb (from patch-scripts) might be useful.
Domen
[-- 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
reply other threads:[~2004-12-20 13:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20041220130238.GB29520@nd47.coderock.org \
--to=domen@coderock.org \
--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.