From: Dan Callaghan <dan.callaghan@opengear.com>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] elfutils: add PACKAGECONFIG for compression algorithms
Date: Wed, 16 Oct 2019 08:46:26 +1000 [thread overview]
Message-ID: <1571178617-sup-8448@galangal.danc.bne.opengear.com> (raw)
In-Reply-To: <84b5c0f5-e790-84e4-967c-6eace1f673ba@intel.com>
[-- Attachment #1: Type: text/plain, Size: 598 bytes --]
Excerpts from Ross Burton's message of 2019-10-15 11:55:31 +01:00:
> If you need bzip-native for the libraries, DEPEND on
> bzip2-replacement-native.
Oh, thanks for the hint! I hadn't seen that trick used before but now
I see it is in quite a few places. I will post a fresh patch using that.
It does seem like it would be simpler to just take bzip2-native out of
ASSUME_PROVIDED, but I guess leaving it in there lets people avoid
building bzip2-native under some circumstances.
--
Dan Callaghan <dan.callaghan@opengear.com>
Software Engineer
Opengear <https://opengear.com/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]
next prev parent reply other threads:[~2019-10-15 22:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 5:48 [PATCH] elfutils: add PACKAGECONFIG for compression algorithms Dan Callaghan
2019-10-15 6:01 ` Dan Callaghan
2019-10-15 6:15 ` [PATCH v2] " Dan Callaghan
2019-10-15 6:59 ` Jacob Kroon
2019-10-15 7:21 ` Dan Callaghan
2019-10-15 7:46 ` Jacob Kroon
2019-10-15 10:55 ` Ross Burton
2019-10-15 22:46 ` Dan Callaghan [this message]
2019-10-16 10:10 ` Ross Burton
2019-10-17 0:46 ` Randy MacLeod
2019-10-16 12:14 ` Richard Purdie
2019-10-15 22:44 ` [PATCH v3] " Dan Callaghan
2019-10-22 12:53 ` Richard Purdie
2019-10-29 20:00 ` Ross Burton
2019-10-29 20:18 ` Adrian Bunk
2019-10-29 20:51 ` Ross Burton
2019-10-29 21:46 ` Dan Callaghan
2019-10-30 23:05 ` Ross Burton
2019-10-16 0:02 ` ✗ patchtest: failure for elfutils: add PACKAGECONFIG for compression algorithms (rev3) Patchwork
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=1571178617-sup-8448@galangal.danc.bne.opengear.com \
--to=dan.callaghan@opengear.com \
--cc=openembedded-core@lists.openembedded.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.