From: Michal Marek <mmarek@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jan Beulich <JBeulich@suse.com>,
dt.tangr@gmail.com, Geert Uytterhoeven <geert@linux-m68k.org>,
James Hogan <james.hogan@imgtec.com>,
Christian Kujau <lists@nerdbynature.de>,
Mike Marciniszyn <mike.marciniszyn@intel.com>,
Nicolas Dichtel <nicolas.dichtel@6wind.com>,
robert.richter@calxeda.com,
"Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>,
zzs0213@gmail.com,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT] kbuild changes for v3.11-rc1
Date: Thu, 11 Jul 2013 15:54:45 +0200 [thread overview]
Message-ID: <20130711135445.GA21500@sepie.suse.cz> (raw)
In-Reply-To: <CA+55aFxtvT3Yvbxe5JGBThZS13payymFJ7jCLyEiE2iNDvsZtQ@mail.gmail.com>
On Wed, Jul 10, 2013 at 07:11:53PM -0700, Linus Torvalds wrote:
> You need to start being more careful. And I would seriously suggest
> you start doing some explicit testing for this. You can do things like
> "find . -user root", and if that shows a single file in the kernel
> tree after a "make [modules_]install", then there's a problem.
Good idea. I added this after the *install calls in my test script.
> Commit d2aae8477cd00325bb7c7c7e95be488088900c48 is broken. It causes
> root to re-write "include/config/kernel.release".
Yeah. It also reveals another bug that we rewrite the kernel.release
file each time. This patch should fix it, but please do not apply it
yet:
>From f522eef24216f229c82b6bbb55f326814db2bac0 Mon Sep 17 00:00:00 2001
From: Michal Marek <mmarek@suse.cz>
Date: Thu, 11 Jul 2013 15:34:51 +0200
Subject: [PATCH] kbuild: Do not overwrite include/config/kernel.release
needlessly
Use filechk to detect if the content changed or not.
diff --git a/Makefile b/Makefile
index 4e3575c..3aa232f 100644
--- a/Makefile
+++ b/Makefile
@@ -794,10 +794,13 @@ PHONY += $(vmlinux-dirs)
$(vmlinux-dirs): prepare scripts
$(Q)$(MAKE) $(build)=$@
+define filechk_kernel.release
+ echo "$(KERNELVERSION)$$($(CONFIG_SHELL) $(srctree)/scripts/setlocalversion $(srctree))"
+endef
+
# Store (new) KERNELRELEASE string in include/config/kernel.release
include/config/kernel.release: include/config/auto.conf FORCE
- $(Q)rm -f $@
- $(Q)echo "$(KERNELVERSION)$$($(CONFIG_SHELL) $(srctree)/scripts/setlocalversion $(srctree))" > $@
+ $(call filechk,kernel.release)
# Things we need to do before we recursively start building the kernel
> There is no excuse for this. That commit is shit. There's no way in
> hell that "make modules_install" should ever rebuild anything, so
> adding that kind of dependency is fundamentally wrong and broken.
We also run dozens of gcc checks during every make invocation, including
make install or make help, so there is some room for improvement. But at
least, these do not write to the source or object tree.
Michal
next prev parent reply other threads:[~2013-07-11 13:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 13:37 [GIT] kbuild changes for v3.11-rc1 Michal Marek
2013-07-11 2:11 ` Linus Torvalds
2013-07-11 4:26 ` Greg KH
2013-07-11 13:54 ` Michal Marek [this message]
2013-07-11 17:16 ` Linus Torvalds
2013-07-12 10:57 ` Robert Richter
2013-07-17 16:05 ` [PATCH] arm, kbuild: make "make install" not depend on vmlinux Robert Richter
2013-07-17 16:36 ` Linus Torvalds
2013-07-17 16:57 ` Robert Richter
2013-07-17 17:03 ` Linus Torvalds
2013-07-18 9:22 ` Michal Marek
2013-09-30 8:49 ` Robert Richter
2013-09-30 16:31 ` Yann E. MORIN
2013-10-09 7:18 ` Geert Uytterhoeven
2013-10-09 10:28 ` Michal Marek
2013-10-09 10:46 ` Geert Uytterhoeven
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=20130711135445.GA21500@sepie.suse.cz \
--to=mmarek@suse.cz \
--cc=JBeulich@suse.com \
--cc=dt.tangr@gmail.com \
--cc=geert@linux-m68k.org \
--cc=james.hogan@imgtec.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
--cc=mike.marciniszyn@intel.com \
--cc=nicolas.dichtel@6wind.com \
--cc=robert.richter@calxeda.com \
--cc=torvalds@linux-foundation.org \
--cc=yselkowitz@users.sourceforge.net \
--cc=zzs0213@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).