From: Keith Owens <kaos@melbourne.sgi.com>
To: LA Walsh <law@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Power usage Q and parallel make question (separate issues)
Date: Thu, 01 Feb 2001 19:24:32 +1100 [thread overview]
Message-ID: <15262.981015872@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Thu, 01 Feb 2001 00:13:17 -0800." <3A791A9D.1B2D0EEA@sgi.com>
On Thu, 01 Feb 2001 00:13:17 -0800,
LA Walsh <law@sgi.com> wrote:
>Keith Owens wrote:
>> It works, until somebody does this
>>
>> make -j 4 modules modules_install
>---
> But that doesn't work now.
Agreed, but letting modules_install parallel run increases the risk of
somebody doing that. Most users will think that they can combine two
parallel runs into a single command, but if they are forced to single
thread modules_install it reduces the risk of user error.
> A bit of documentation at the beginning of the Makefile would do wonders
>for kernel-developer (not end user, please!) clarity. I've oft'asked the question
>as to what really is supported. I've tried things like make dep bzImage modules --
>I noticed it didn't work fairly quickly. Same with modules/modules_install --
>people would probably figure that one out, but just a bit of documentation would
>help even that.
The 2.5 kbuild system will be fully documented, all the way from
reasons for doing things down to how they are down. Trust me on this!
I have had too many problems with undocumented changes in kbuild.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-02-01 8:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 19:44 Power usage Q and parallel make question (separate issues) LA Walsh
2001-02-01 0:32 ` Keith Owens
2001-02-01 3:02 ` LA Walsh
2001-02-01 3:32 ` Keith Owens
2001-02-01 8:13 ` LA Walsh
2001-02-01 8:24 ` Keith Owens [this message]
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=15262.981015872@ocs3.ocs-net \
--to=kaos@melbourne.sgi.com \
--cc=law@sgi.com \
--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