From: "Jan Beulich" <jbeulich@novell.com>
To: <sam@ravnborg.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: your change to prevent needless re-building of vmlinux.o
Date: Fri, 16 May 2008 17:08:09 +0100 [thread overview]
Message-ID: <482DCD89.76E4.0078.0@novell.com> (raw)
Sam,
while also looking into this issue (found time only now) I realized this is
already worked around in .26-rc2. However, it would seem to me that
suppressing the dependency on init/built-in.o altogether is likely to
cause problems in the future. Going through the version generating
logic again I realized that since vmlinux.o is always built before the first
of the (perhaps multiple, due to kallsyms) final linking stages, it ought
to be possible to simply move the version generation into the vmlinux.o
rule. And indeed, this
define rule_vmlinux-modpost
:
+$(call cmd,vmlinux_version)
+$(call cmd,vmlinux-modpost)
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.modpost $@
$(Q)echo 'cmd_$@ := $(cmd_vmlinux-modpost)' > $(dot-target).cmd
endef
with the two other invocations of vmlinux_version removed, seems to
do what is wanted.
What do you think? Am I overlooking some aspect here?
Btw., another slight anomaly I noticed is that modpost on the modules
is always performed (even when nothing changed in the tree), while
on vmlinux.o it is only performed when something caused a re-link. Is
that intentional, or just a to-be-tolerated side effect?
Thanks, Jan
next reply other threads:[~2008-05-16 16:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 16:08 Jan Beulich [this message]
2008-05-17 12:52 ` your change to prevent needless re-building of vmlinux.o Sam Ravnborg
2008-05-18 18:52 ` [RFC PATCH] move link of vmlinux from Makefile to a script Sam Ravnborg
2008-05-19 7:42 ` Jan Beulich
2008-05-19 8:19 ` Sam Ravnborg
2008-05-19 8:35 ` Jan Beulich
2008-05-19 7:36 ` your change to prevent needless re-building of vmlinux.o Jan Beulich
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=482DCD89.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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