linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: "mmarek@suse.com" <mmarek@suse.com>
Cc: "Vineet.Gupta1@synopsys.com" <Vineet.Gupta1@synopsys.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>,
	"linux-snps-arc@lists.infradead.org" 
	<linux-snps-arc@lists.infradead.org>
Subject: Re: [PATCH 3/6] arc: Use full path in KBUILD_IMAGE definition
Date: Wed, 23 Nov 2016 19:40:15 +0000	[thread overview]
Message-ID: <1479929955.3931.28.camel@synopsys.com> (raw)
In-Reply-To: <20161122213434.14788-3-mmarek@suse.com>

Hi Michal,

On Tue, 2016-11-22 at 22:34 +0100, Michal Marek wrote:
> The KBUILD_IMAGE variable is used by the rpm and deb-pkg targets, which
> expect it to point to the image file in the build directory. The
> builddeb script has a workaround for architectures which only provide
> the basename, but let's provide a clean interface for packaging tools.
> 
> Cc: Vineet Gupta <vgupta@synopsys.com>
> Cc: linux-snps-arc@lists.infradead.org
> Signed-off-by: Michal Marek <mmarek@suse.com>
> ---
>  arch/arc/Makefile | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/arc/Makefile b/arch/arc/Makefile
> index 19cce226d1a8..44ef35d33956 100644
> --- a/arch/arc/Makefile
> +++ b/arch/arc/Makefile
> @@ -123,9 +123,9 @@ libs-y		+= arch/arc/lib/ $(LIBGCC)
>  boot		:= arch/arc/boot
>  
>  #default target for make without any arguments.
> -KBUILD_IMAGE	:= bootpImage
> +KBUILD_IMAGE	:= $(boot)/bootpImage
>  
> -all:	$(KBUILD_IMAGE)
> +all:	bootpImage
>  bootpImage: vmlinux
>  
>  boot_targets += uImage uImage.bin uImage.gz

I tried to find any examples on how that KBUILD_IMAGE thingy is used
but to no avail. It looks like for ARC "bootpImage" makes not much
sense and if you really want to get something useful in .deb/.rpm
most probably something like below may work much better:
------------------------>8--------------------------
KBUILD_IMAGE	:= $(boot)/uImage
------------------------>8--------------------------

And I don't know context of KBUILD_IMAGE usage but in
case of ARC our default target is "vmlinux" so I'm not sure then if
KBUILD_IMAGE may point to non-default target.

For example in "arch/avr32/Makefile" I see more complicated construction:
------------------------>8--------------------------
             KBUILD_IMAGE := $(boot)/uImage
vmlinux.elf: KBUILD_IMAGE := $(boot)/vmlinux.elf
vmlinux.cso: KBUILD_IMAGE := $(boot)/vmlinux.cso
uImage.srec: KBUILD_IMAGE := $(boot)/uImage.srec
uImage:      KBUILD_IMAGE := $(boot)/uImage
------------------------>8--------------------------
and may imagine that we need something similar for ARC obviously with
default being "$(boot)/vmlinux".

-Alexey

  reply	other threads:[~2016-11-23 19:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-22 21:34 [PATCH 1/6] arm64: Use full path in KBUILD_IMAGE definition Michal Marek
2016-11-22 21:34 ` [PATCH 2/6] arm: " Michal Marek
2017-03-20 13:53   ` Masahiro Yamada
2016-11-22 21:34 ` [PATCH 3/6] arc: " Michal Marek
2016-11-23 19:40   ` Alexey Brodkin [this message]
2016-11-25 14:21     ` Michal Marek
2017-03-20 13:54   ` Masahiro Yamada
2016-11-22 21:34 ` [PATCH 4/6] sh: " Michal Marek
2017-03-20 13:54   ` Masahiro Yamada
2016-11-22 21:34 ` [PATCH 5/6] unicore32: " Michal Marek
2017-03-20 13:55   ` Masahiro Yamada
2016-11-22 21:34 ` [PATCH 6/6] deb-pkg: Remove the KBUILD_IMAGE workaround Michal Marek
2016-11-25 12:12   ` Riku Voipio
2016-11-25 14:22     ` Michal Marek
2017-03-20 13:56       ` Masahiro Yamada
2017-03-10 17:58 ` [PATCH 1/6] arm64: Use full path in KBUILD_IMAGE definition Will Deacon
2017-03-10 21:20   ` Michal Marek
2017-03-18 13:14     ` Masahiro Yamada
2017-03-20 12:13       ` Will Deacon
2017-03-20 13:52         ` Masahiro Yamada

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=1479929955.3931.28.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.com \
    --cc=Vineet.Gupta1@synopsys.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.org \
    --cc=mmarek@suse.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;
as well as URLs for NNTP newsgroup(s).