From: William Park <opengeometry@yahoo.ca>
To: "Linux kernel mailing list (lkml)" <linux-kernel@vger.kernel.org>
Subject: Re: Safety of -j N when building kernels?
Date: Wed, 22 May 2002 13:24:04 -0400 [thread overview]
Message-ID: <20020522132404.A449@node1.opengeometry.ca> (raw)
In-Reply-To: <20020522165320.GC18059@lanl.gov>
On Wed, May 22, 2002 at 10:53:20AM -0600, Eric Weigle wrote:
> Ok, stupid question of the moment-
>
> I always read about the kernel compilation benchmarks people run on the
> ultra-snazzy new machines, but do people actually run the kernels thus
> generated?
>
> I have visions of a process being backgrounded to generate some files, and
> not completing before the one of the old files gets linked into the kernel
> (because not all files were listed as dependencies, for example).
>
> So are the kernel's current Makefiles really SMP safe -- can one really
> run multiple jobs when building Linux kernels? Any horror stories, or am
> I just paranoid?
I usually do
make menuconfig
make -j3 dep
make -j3 bzImage modules
make -j3 bzlilo modules_install
where I separate the compile and install part. But, this depends on what
you are compiling. I usually have problem with Compaq and Hamradio stuffs,
so I have them commented out.
--
William Park, Open Geometry Consulting, <opengeometry@yahoo.ca>
8-CPU Cluster, Hosting, NAS, Linux, LaTeX, python, vim, mutt, tin
next prev parent reply other threads:[~2002-05-22 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 16:53 Safety of -j N when building kernels? Eric Weigle
2002-05-22 17:24 ` William Park [this message]
2002-05-22 17:31 ` Fernando [Quatro]
2002-05-22 18:29 ` Samuel Flory
2002-05-22 20:03 ` James Stevenson
2002-05-22 23:32 ` Keith Owens
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=20020522132404.A449@node1.opengeometry.ca \
--to=opengeometry@yahoo.ca \
--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