From: James Antill <james@and.org>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: Muli Ben-Yehuda <mulix@actcom.co.il>,
William Lee Irwin III <wli@holomorphy.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: PATCH: compile the kernel with -Werror
Date: 16 Jul 2002 16:36:49 -0400 [thread overview]
Message-ID: <m3it3fo1em.fsf@code.and.org> (raw)
In-Reply-To: <200207131541.37310.roy@karlsbakk.net>
Roy Sigurd Karlsbakk <roy@karlsbakk.net> writes:
> On Saturday 13 July 2002 09:26, Muli Ben-Yehuda wrote:
> > A full kernel compilation, especially when using the -j switch to
> > make, can cause warnings to "fly off the screen" without the user
> > noticing them. For example, wli's patch lazy_buddy.2.5.25-1 of today
> > had a missing return statement in a function returning non void, which
> > the compiler probably complained about but the warning got lost in the
> > noise (a little birdie told me wli used -j64).
>
> Why not add a menu item under kernel hacking?
FFS....
make bzImage > compile.log 2> errors.log
--
James Antill -- james@and.org
"Although I have found authors who assert that the use of internal loop exits
is wrong, I have encountered none that support their claims with objective
evidence." -- Eric S. Roberts, Loop Exits and Structured Programming
next prev parent reply other threads:[~2002-07-16 20:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-13 7:26 PATCH: compile the kernel with -Werror Muli Ben-Yehuda
2002-07-13 8:02 ` Zwane Mwaikambo
2002-07-13 7:43 ` Muli Ben-Yehuda
2002-07-13 14:49 ` Thunder from the hill
2002-07-13 8:17 ` Mike Galbraith
2002-07-13 13:10 ` Kenneth Johansson
2002-07-13 13:41 ` Roy Sigurd Karlsbakk
2002-07-13 14:59 ` Alan Cox
2002-07-16 20:36 ` James Antill [this message]
2002-07-13 14:24 ` Alan Cox
2002-07-13 13:34 ` William Lee Irwin III
2002-07-13 18:46 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2002-07-13 21:31 Dan Kegel
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=m3it3fo1em.fsf@code.and.org \
--to=james@and.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mulix@actcom.co.il \
--cc=roy@karlsbakk.net \
--cc=wli@holomorphy.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