Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/7] core: add generic support for lz archives
Date: Thu, 9 Feb 2017 22:16:35 +0100	[thread overview]
Message-ID: <20170209221635.2c003010@gmx.net> (raw)
In-Reply-To: <20170209211128.ssawhi6brgz7dh5q@tarshish>

Hello Baruch,

On Thu, 9 Feb 2017 23:11:28 +0200, Baruch Siach <baruch@tkos.co.il> wrote:

> Hi Peter,
> 
> On Thu, Feb 09, 2017 at 11:00:37PM +0200, Baruch Siach wrote:
> > On Thu, Feb 09, 2017 at 09:26:12PM +0100, Peter Seiderer wrote:
> > > On Thu,  9 Feb 2017 21:50:14 +0200, Baruch Siach <baruch@tkos.co.il> wrote:
> > > > This commit teaches the generic code how to extract .tar.lz archives. When
> > > > lzip is not installed on the host, host-lzip gets built automatically.
> > > > 
> > > 
> > > On my host there is no lzip installed, with your patches applied I get the following
> > > error message:
> > > 
> > > which: no lzip in (/home/seiderer/Work/build_arm_qt5_stdcpp11_001/host/usr/bin)
> > > You must install '/home/seiderer/Work/build_arm_qt5_stdcpp11_001/host/usr/bin/lzip' on your build machine
> > > support/dependencies/dependencies.mk:22: recipe for target 'core-dependencies' failed
> > > make[1]: *** [core-dependencies] Error 1
> > > Makefile:16: recipe for target '_all' failed
> > > make: *** [_all] Error 2
> > 
> > Thanks for testing.
> > 
> > Does this fixes your problem?
> > 
> > diff --git a/package/pkg-generic.mk b/package/pkg-generic.mk
> > index 303dda090daa..eb01c2fa0e2f 100644
> > --- a/package/pkg-generic.mk
> > +++ b/package/pkg-generic.mk
> > @@ -930,7 +930,7 @@ endif # SITE_METHOD
> >  # ZCAT="gzip -d -c", and to check for the dependency we only want 'gzip'.
> >  # Remove xzcat/lzip from the list of required dependencies, as they get built
> >  # automatically if they're not found.
> > -DL_TOOLS_DEPENDENCIES += $$(filter-out xzcat lzip,$$(firstword $$(call suitable-extractor,$$($(2)_SOURCE))))
> > +DL_TOOLS_DEPENDENCIES += $$(filter-out xzcat lzip,$$(notdir $$(firstword $$(call suitable-extractor,$$($(2)_SOURCE)))))


Fixes my test case too, I tried:

DL_TOOLS_DEPENDENCIES += $$(filter-out $(HOST_DIR)/usr/bin/xzcat $(HOST_DIR)/usr/bin/lzip,$$(firstword $$(call suitable-extractor,$$($(2)_SOURCE))))

Regards,
Peter


> >  
> >  # Ensure all virtual targets are PHONY. Listed alphabetically.
> >  .PHONY:	$(1) \
> 
> Thinking about it again, this is clearly not the right solution. It breaks 
> custom BR2_LZCAT. I'll try to come up with something better.
> 
> baruch
> 

  reply	other threads:[~2017-02-09 21:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-09 19:50 [Buildroot] [PATCH 1/7] lzip: use the more informative homepage link Baruch Siach
2017-02-09 19:50 ` [Buildroot] [PATCH 2/7] lzip: bump to version 1.18 Baruch Siach
2017-02-09 20:36   ` Thomas Petazzoni
2017-02-09 19:50 ` [Buildroot] [PATCH 3/7] core: add generic support for lz archives Baruch Siach
2017-02-09 20:26   ` Peter Seiderer
2017-02-09 21:00     ` Baruch Siach
2017-02-09 21:11       ` Baruch Siach
2017-02-09 21:16         ` Peter Seiderer [this message]
2017-02-09 21:33           ` Baruch Siach
2017-02-09 19:50 ` [Buildroot] [PATCH 4/7] ed: use generic extract command Baruch Siach
2017-02-09 19:50 ` [Buildroot] [PATCH 5/7] ddrescue: " Baruch Siach
2017-02-09 19:50 ` [Buildroot] [PATCH 6/7] ocrad: " Baruch Siach
2017-02-09 19:50 ` [Buildroot] [PATCH 7/7] ddrescue: fix target build Baruch Siach
2017-02-09 20:40   ` Thomas Petazzoni
2017-02-09 20:52     ` Baruch Siach
2017-02-09 20:56     ` Peter Seiderer
2017-02-09 20:36 ` [Buildroot] [PATCH 1/7] lzip: use the more informative homepage link 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=20170209221635.2c003010@gmx.net \
    --to=ps.report@gmx.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox