From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] pixz: Add 1.0.6
Date: Mon, 11 Jan 2016 09:36:36 +1300 [thread overview]
Message-ID: <1771478.km9IAYYp8Q@peggleto-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <3794662.0pqDkncOgQ@peggleto-mobl.ger.corp.intel.com>
On Mon, 11 Jan 2016 09:26:39 Paul Eggleton wrote:
> On Fri, 08 Jan 2016 18:22:49 Richard Purdie wrote:
> > xz gives better compression results than bzip/gz but is often slower.
> > Using parallel compression mitigates this somewhat and is particularly
> > useful for the SDK.
> >
> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> >
> > diff --git a/meta/recipes-support/pixz/pixz_1.0.6.bb
> > b/meta/recipes-support/pixz/pixz_1.0.6.bb new file mode 100644
> > index 0000000..e6e4ac2
> > --- /dev/null
> > +++ b/meta/recipes-support/pixz/pixz_1.0.6.bb
> > @@ -0,0 +1,14 @@
> > +SUMMARY = "Parallel, indexed xz compressor"
> > +
> > +DEPENDS = "xz libarchive"
> > +
> > +SRC_URI =
> > "https://github.com/vasi/pixz/releases/download/v${PV}/${BPN}-${PV}.tar.xz
> > "
>
> Can we rely on this never changing? I thought we'd experienced problems with
> github's release tarballs being generated on the fly in the past...
Another thing, this seems to fail to build without asciidoc:
------------ snip ------------
checking for src/pixz.1... no
checking for a2x... no
configure: error: AsciiDoc not found, not able to generate the man page.
------------ snip ------------
This is also related to not supporting B != S, since src/pixz.1 does exist,
just in S and not B. If you inherit autotools-brokensep instead of autotools
it works.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2016-01-10 20:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 18:22 [PATCH] pixz: Add 1.0.6 Richard Purdie
2016-01-09 17:14 ` Khem Raj
2016-01-11 18:37 ` Andre McCurdy
2016-01-10 20:26 ` Paul Eggleton
2016-01-10 20:36 ` Paul Eggleton [this message]
2016-01-11 21:07 ` Paul Eggleton
2016-01-11 21:17 ` Khem Raj
2016-01-11 22:36 ` Paul Eggleton
2016-01-11 23:07 ` Khem Raj
2016-01-11 23:21 ` Khem Raj
2016-01-11 23:35 ` Richard Purdie
2016-01-12 0:17 ` Khem Raj
2016-01-11 13:37 ` Burton, Ross
2016-01-11 18:52 ` Randy Witt
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=1771478.km9IAYYp8Q@peggleto-mobl.ger.corp.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox