All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: "H. J. Lu" <hjl@lucon.org>
Cc: linux kernel <linux-kernel@vger.kernel.org>,
	linux ia64 kernel <linux-ia64@vger.kernel.org>
Subject: Re: Does parallel make work for modules?
Date: Tue, 22 Jun 2004 23:09:52 +0000	[thread overview]
Message-ID: <40D8BC40.9030104@pobox.com> (raw)
In-Reply-To: <20040622220813.GA306@lucon.org>

H. J. Lu wrote:
> When building 2.6.7 on a 4way Linux/ia64, "make -j4 modules" doesn't
> spawn 4 jobs. I got


BTW, you don't need to bother with a separate 'make modules' step anymore.

'make -jN' should build everything, including the default boot image for 
your architecture.

	Jeff



WARNING: multiple messages have this Message-ID (diff)
From: Jeff Garzik <jgarzik@pobox.com>
To: "H. J. Lu" <hjl@lucon.org>
Cc: linux kernel <linux-kernel@vger.kernel.org>,
	linux ia64 kernel <linux-ia64@vger.kernel.org>
Subject: Re: Does parallel make work for modules?
Date: Tue, 22 Jun 2004 19:09:52 -0400	[thread overview]
Message-ID: <40D8BC40.9030104@pobox.com> (raw)
In-Reply-To: <20040622220813.GA306@lucon.org>

H. J. Lu wrote:
> When building 2.6.7 on a 4way Linux/ia64, "make -j4 modules" doesn't
> spawn 4 jobs. I got


BTW, you don't need to bother with a separate 'make modules' step anymore.

'make -jN' should build everything, including the default boot image for 
your architecture.

	Jeff



  parent reply	other threads:[~2004-06-22 23:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-22 22:08 Does parallel make work for modules? H. J. Lu
2004-06-22 22:08 ` H. J. Lu
2004-06-22 22:27 ` Keith Owens
2004-06-22 22:27   ` Keith Owens
2004-06-22 23:09 ` Jeff Garzik [this message]
2004-06-22 23:09   ` Jeff Garzik
2004-06-22 23:40 ` Kalin KOZHUHAROV

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=40D8BC40.9030104@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=hjl@lucon.org \
    --cc=linux-ia64@vger.kernel.org \
    --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 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.