diff options
| author | Mike Waychison <mikew@google.com> | 2011-03-15 09:34:25 +0300 |
|---|---|---|
| committer | Michal Marek <mmarek@suse.cz> | 2011-03-17 14:29:20 +0300 |
| commit | e1b702cf224df446b4ce0416dfb02858e7cc068b (patch) | |
| tree | dd64df66e3231a903adb0e536448b0b0b4998a59 /scripts | |
| parent | 4a5838ad9d2d4f7354a310982483f4c76aa0abeb (diff) | |
| download | linux-e1b702cf224df446b4ce0416dfb02858e7cc068b.tar.xz | |
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 'scripts')
| -rw-r--r-- | scripts/Makefile | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/scripts/Makefile b/scripts/Makefile index 2e088109fbd5..fcea26168bca 100644 --- a/scripts/Makefile +++ b/scripts/Makefile @@ -18,6 +18,11 @@ always := $(hostprogs-y) $(hostprogs-m) # The following hostprogs-y programs are only build on demand hostprogs-y += unifdef +# This target is used internally to avoid "is up to date" messages +PHONY += build_unifdef +build_unifdef: scripts/unifdef FORCE + @: + subdir-$(CONFIG_MODVERSIONS) += genksyms subdir-y += mod subdir-$(CONFIG_SECURITY_SELINUX) += selinux |