linux-kernel - Re: [PATCH] KBuild: silence "'scripts/unifdef' is up to date."

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Thu, 17 Mar 2011 12:32:55 +0100
From:	Michal Marek <mmarek@...e.cz>
To:	WANG Cong <xiyou.wangcong@...il.com>
Cc:	linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] KBuild: silence "'scripts/unifdef' is up to date."

On Tue, Mar 15, 2011 at 01:40:37PM +0000, WANG Cong wrote:
> On Mon, 14 Mar 2011 23:34:25 -0700, Mike Waychison wrote:
> 
> > Patch applies to 2.6.38-rc8.
> > 
> > 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@...gle.com> ---
> 
> Acked-by: WANG Cong <xiyou.wangcong@...il.com>

Applied to kbuild-2.6.git#kbuild, thanks.

Michal
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/