All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Andrew Worsley <amworsley@gmail.com>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: [Patch] scripts: fix "make install" when a directory or file named install exists
Date: Thu, 30 Aug 2012 15:30:48 +0200	[thread overview]
Message-ID: <503F6B08.3000007@suse.cz> (raw)
In-Reply-To: <CA+Y=x3k4eMMamEANrSFGcopAesMqrbQP-gcxvyXpV7SEee4hOw@mail.gmail.com>

On 7.8.2012 11:08, Andrew Worsley wrote:
> diff --git a/scripts/Makefile.build b/scripts/Makefile.build
> index ff1720d..cf4b970 100644
> --- a/scripts/Makefile.build
> +++ b/scripts/Makefile.build
> @@ -434,6 +434,7 @@ $(multi-used-m) : %.o: $(multi-objs-m) FORCE
> 
>  targets += $(multi-used-y) $(multi-used-m)
> 
> +PHONY += install
> 
>  # Descending
>  # ---------------------------------------------------------------------------

I don't think this is the right place to fix it (at least, it should be
near the .PHONY target with an explanation why it is needed). First, the
PHONY variable is usually assigned right before the target is defined.
Second, the are usually two 'install' targets: One is in
arch/$arch/Makefile, which usually invokes scripts/Makefile.build in
arch/$arch/boot, where the actual install target is defined. So this
patch only covers the arch/$arch/boot/Makefile case. It works on x86,
because arch/x86/Makefile already has the PHONY assignment and only
arch/x86/boot/Makefile is missing it. Also, not all architectures have
install, while some have more *install variants. So I'm for fixing the
Makefiles that do not yet have the PHONY += install or such.

Michal

      reply	other threads:[~2012-08-30 13:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-07  9:08 [Patch] scripts: fix "make install" when a directory or file named install exists Andrew Worsley
2012-08-30 13:30 ` 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=503F6B08.3000007@suse.cz \
    --to=mmarek@suse.cz \
    --cc=amworsley@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.