From: William Lee Irwin III <wli@holomorphy.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Andrew Morton <akpm@osdl.org>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.8.1-mm1: parallel make doesn't.
Date: Tue, 17 Aug 2004 17:08:26 -0700 [thread overview]
Message-ID: <20040818000826.GR11200@holomorphy.com> (raw)
In-Reply-To: <1092787271.27346.118.camel@bach>
On Wed, Aug 18, 2004 at 10:01:11AM +1000, Rusty Russell wrote:
> Need to make the first few files without -j, othewise it barfs. This is
> a regression over 2.6.8.1 (sorry, don't know when it crept into the -mm
> tree). .config attached in case it matters.
> cd ~/devel/kernel/.28758-linux-2.6.8.1-mm1.updated/
> make -j5
> CHK include/linux/version.h
> SYMLINK include/asm -> include/asm-i386
> UPD include/linux/version.h
> SPLIT include/linux/autoconf.h -> include/config/*
> make: *** No rule to make target `.tmp_kallsyms2.S', needed by
> `.tmp_kallsyms2.o'. Stop.
> make: *** Waiting for unfinished jobs....
> make: *** Waiting for unfinished jobs....
> make: *** Waiting for unfinished jobs....
> Compilation exited abnormally with code 2 at Wed Aug 18 09:54:47
Sam Ravnborg already posted a fix. Yes, the semicolon is necessary.
Index: mm1-2.6.8.1/Makefile
===================================================================
--- mm1-2.6.8.1.orig/Makefile 2004-08-16 23:47:11.979962024 -0700
+++ mm1-2.6.8.1/Makefile 2004-08-17 00:03:56.918188192 -0700
@@ -610,6 +610,8 @@
.tmp_vmlinux3: $(vmlinux-objs) .tmp_kallsyms2.o arch/$(ARCH)/kernel/vmlinux.lds FORCE
$(call if_changed_rule,vmlinux__)
+$(KALLSYMS): scripts;
+
endif
# Finally the vmlinux rule
prev parent reply other threads:[~2004-08-18 0:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 0:01 2.6.8.1-mm1: parallel make doesn't Rusty Russell
2004-08-18 0:08 ` William Lee Irwin III [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=20040818000826.GR11200@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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.