From: Krzysztof Helt <krzysztof.h1@wp.pl>
To: sparclinux@vger.kernel.org
Subject: Makefile improvement for 2.4 kernel
Date: Mon, 14 Feb 2005 19:23:25 +0000 [thread overview]
Message-ID: <4210FAAD.3010903@wp.pl> (raw)
[-- Attachment #1: Type: text/plain, Size: 497 bytes --]
Here is a atch which forces the arch/sparc/boot directory being built
after all other arch/sparc/* directories. On my 2-way SS20 it makes
"make -j3 vmlinux" working in the first pass. Someone can test it on
machine with more CPUs. I post it here for judgement if it is a correct
way to force the correct order of kernel build. I am not sure if I can
use variables from the main makefile int the arch/sparc/Makefile.
If it is useful, please merge it into the kernel tree.
Regards,
Krzysztof
[-- Attachment #2: smp-makefile.patch --]
[-- Type: text/x-patch, Size: 871 bytes --]
--- arch/sparc/Makefile.old 2004-12-08 22:26:06.000000000 +0100
+++ arch/sparc/Makefile 2005-02-14 19:13:22.000000000 +0100
@@ -35,7 +35,7 @@
HEAD := arch/sparc/kernel/head.o arch/sparc/kernel/init_task.o
-SUBDIRS += arch/sparc/kernel arch/sparc/lib arch/sparc/prom \
+PRE_BT_SUBDIRS := arch/sparc/kernel arch/sparc/lib arch/sparc/prom \
arch/sparc/mm arch/sparc/math-emu
CORE_FILES := arch/sparc/kernel/kernel.o arch/sparc/mm/mm.o $(CORE_FILES) \
@@ -45,10 +45,13 @@
$(TOPDIR)/arch/sparc/lib/lib.a
# This one has to come last
-SUBDIRS += arch/sparc/boot
+SUBDIRS += $(PRE_BT_SUBDIRS) arch/sparc/boot
CORE_FILES_NO_BTFIX := $(CORE_FILES)
CORE_FILES += arch/sparc/boot/btfix.o
+# The boot dir should be built as the last one
+$(patsubst %, _dir_%, arch/sparc/boot ): $(patsubst %, _dir_%, $(PRE_BT_SUBDIRS) )
+
export CORE_FILES_NO_BTFIX
archclean:
reply other threads:[~2005-02-14 19:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4210FAAD.3010903@wp.pl \
--to=krzysztof.h1@wp.pl \
--cc=sparclinux@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.