From: Kenneth Johansson <ken@kenjo.org>
To: Muli Ben-Yehuda <mulix@actcom.co.il>
Cc: Linus Torvalds <torvalds@transmeta.com>,
William Lee Irwin III <wli@holomorphy.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: PATCH: compile the kernel with -Werror
Date: 13 Jul 2002 15:10:20 +0200 [thread overview]
Message-ID: <1026565820.13069.5.camel@tiger> (raw)
In-Reply-To: <20020713102615.H739@alhambra.actcom.co.il>
On Sat, 2002-07-13 at 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).
use
make -j64 KBUILD_VERBOSE=0
This is similar to what kbuils2.5 dose by default but since the in
kernel version do not have one single makefile the output gets a bit
reshuffled.
But -j64 dose seem a but hi I usually use the same as numbers of cpu.
over nfs I go a little higher.
next prev parent reply other threads:[~2002-07-13 13:08 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 [this message]
2002-07-13 13:41 ` Roy Sigurd Karlsbakk
2002-07-13 14:59 ` Alan Cox
2002-07-16 20:36 ` James Antill
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=1026565820.13069.5.camel@tiger \
--to=ken@kenjo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mulix@actcom.co.il \
--cc=torvalds@transmeta.com \
--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 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.