All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 2/5] package: add generic support for lz archives
Date: Wed, 15 Feb 2017 22:15:20 +0100	[thread overview]
Message-ID: <20170215221520.41e4c66e@free-electrons.com> (raw)
In-Reply-To: <1e78e6f82883e4ba95766459a39cbd2d49934152.1486930542.git.baruch@tkos.co.il>

Hello,

On Sun, 12 Feb 2017 22:15:39 +0200, Baruch Siach wrote:

> diff --git a/Makefile b/Makefile
> index df3b64eb03ec..b4550e098958 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -431,6 +431,7 @@ KERNEL_ARCH := $(shell echo "$(ARCH)" | sed -e "s/-.*//" \
>  ZCAT := $(call qstrip,$(BR2_ZCAT))
>  BZCAT := $(call qstrip,$(BR2_BZCAT))
>  XZCAT := $(call qstrip,$(BR2_XZCAT))
> +LZCAT := $(call qstrip,$(BR2_LZCAT))

So here, we use the value of the config option BR2_LZCAT.

> diff --git a/support/dependencies/check-host-lzip.mk b/support/dependencies/check-host-lzip.mk
> new file mode 100644
> index 000000000000..708105acd892
> --- /dev/null
> +++ b/support/dependencies/check-host-lzip.mk
> @@ -0,0 +1,5 @@
> +ifeq (,$(call suitable-host-package,lzip,$(LZCAT)))
> +DEPENDENCIES_HOST_PREREQ += host-lzip
> ++EXTRACTOR_DEPENDENCY_PRECHECKED_EXTENSIONS += .lz
> +LZCAT = $(HOST_DIR)/usr/bin/lzip -d -c

But here in the case where we are building our own host-lzip, we
completely ignore BR2_LZCAT, and use a hardcoded
$(HOST_DIR)/usr/bin/lzip -d -c.

Since there is already the exact same pattern for XZCAT, I decided to
apply your patch anyway. I also don't really understand the use case
for all those BR2_ZCAT, BR2_BZCAT, BR2_XZCAT, etc. config options.
Peter, maybe you can shed some light on why we have these?

Also Baruch: there was one too many "+" at the beginning of:

> ++EXTRACTOR_DEPENDENCY_PRECHECKED_EXTENSIONS += .lz

so I've fixed that before applying.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  parent reply	other threads:[~2017-02-15 21:15 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-12 20:15 [Buildroot] [PATCH v3 1/5] package: refactor listing of extractor dependencies Baruch Siach
2017-02-12 20:15 ` [Buildroot] [PATCH v3 2/5] package: add generic support for lz archives Baruch Siach
2017-02-14 13:43   ` Thomas De Schampheleire
2017-02-15 21:15   ` Thomas Petazzoni [this message]
2017-02-15 22:48     ` Arnout Vandecappelle
2017-02-16  7:32       ` Thomas Petazzoni
2017-02-16  8:25         ` Arnout Vandecappelle
2017-02-16  8:34           ` Thomas Petazzoni
2017-02-16 17:24             ` Arnout Vandecappelle
2017-02-16 17:41       ` Yann E. MORIN
2017-02-16 22:03         ` Peter Korsgaard
2017-02-16 22:11           ` Yann E. MORIN
2017-02-17  7:43             ` Arnout Vandecappelle
2017-02-17 17:07               ` Yann E. MORIN
2017-02-16 22:08       ` Peter Korsgaard
2017-02-16  8:36     ` Thomas De Schampheleire
2017-02-16  8:40       ` Thomas Petazzoni
2017-02-16 10:24         ` Thomas De Schampheleire
2017-02-21 21:55   ` [Buildroot] Bug in "package: add generic support for lz archives" ? Thomas Petazzoni
2017-02-22  5:32     ` Baruch Siach
2017-02-22  8:03       ` Thomas Petazzoni
2017-02-12 20:15 ` [Buildroot] [PATCH v3 3/5] ed: use generic extract command Baruch Siach
2017-02-12 20:15 ` [Buildroot] [PATCH v3 4/5] ddrescue: " Baruch Siach
2017-02-12 20:15 ` [Buildroot] [PATCH v3 5/5] ocrad: " Baruch Siach
2017-02-14 13:42 ` [Buildroot] [PATCH v3 1/5] package: refactor listing of extractor dependencies Thomas De Schampheleire
2017-02-14 21:39 ` Thomas Petazzoni
2017-02-15  7:04   ` Baruch Siach
2017-02-15 21:13 ` Thomas Petazzoni

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=20170215221520.41e4c66e@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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.