aboutsummaryrefslogtreecommitdiffstats
path: root/Makefile
diff options
context:
space:
mode:
authorMike Waychison <mikew@google.com>2011-03-15 02:34:25 -0400
committerMichal Marek <mmarek@suse.cz>2011-03-17 07:29:20 -0400
commite1b702cf224df446b4ce0416dfb02858e7cc068b (patch)
treedd64df66e3231a903adb0e536448b0b0b4998a59 /Makefile
parent4a5838ad9d2d4f7354a310982483f4c76aa0abeb (diff)
KBuild: silence "'scripts/unifdef' is up to date."
While changing our build system over to use the headers_install target as part of our klibc build, the following message started showing up in our logs: make[2]: `scripts/unifdef' is up to date. It turns out that the build blindly invokes a recursive make on this target, which causes make to emit this message when the target is already up to date. This isn't seen for most targets as the rest of the build relies primarily on the default target and on PHONY targets when invoking make recursively. Silence the above message when building unifdef as part of headers_install by hiding it behind a new PHONY target called "build_unifdef" that has an empty recipe. Signed-off-by: Mike Waychison <mikew@google.com> Acked-by: WANG Cong <xiyou.wangcong@gmail.com> Signed-off-by: Michal Marek <mmarek@suse.cz>
Diffstat (limited to 'Makefile')
-rw-r--r--Makefile2
1 files changed, 1 insertions, 1 deletions
diff --git a/Makefile b/Makefile
index 2b1e37da2bb5..0bf29dcc66fc 100644
--- a/Makefile
+++ b/Makefile
@@ -1022,7 +1022,7 @@ hdr-dst = $(if $(KBUILD_HEADERS), dst=include/asm-$(hdr-arch), dst=include/asm)
1022 1022
1023PHONY += __headers 1023PHONY += __headers
1024__headers: include/linux/version.h scripts_basic FORCE 1024__headers: include/linux/version.h scripts_basic FORCE
1025 $(Q)$(MAKE) $(build)=scripts scripts/unifdef 1025 $(Q)$(MAKE) $(build)=scripts build_unifdef
1026 1026
1027PHONY += headers_install_all 1027PHONY += headers_install_all
1028headers_install_all: 1028headers_install_all: