public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: WANG Cong <xiyou.wangcong@gmail.com>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KBuild: silence "'scripts/unifdef' is up to date."
Date: Thu, 17 Mar 2011 12:32:55 +0100	[thread overview]
Message-ID: <20110317113255.GA28330@sepie.suse.cz> (raw)
In-Reply-To: <ilnq8l$rjj$1@dough.gmane.org>

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@google.com> ---
> 
> Acked-by: WANG Cong <xiyou.wangcong@gmail.com>

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

Michal

      reply	other threads:[~2011-03-17 11:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15  6:34 [PATCH] KBuild: silence "'scripts/unifdef' is up to date." Mike Waychison
2011-03-15 13:40 ` WANG Cong
2011-03-17 11:32   ` Michal Marek [this message]

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=20110317113255.GA28330@sepie.suse.cz \
    --to=mmarek@suse.cz \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xiyou.wangcong@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