From: Ross Burton <ross.burton@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v3] elfutils: add PACKAGECONFIG for compression algorithms
Date: Tue, 29 Oct 2019 20:51:17 +0000 [thread overview]
Message-ID: <ea2156a7-8f39-ffdc-55ca-6488b115eb2b@intel.com> (raw)
In-Reply-To: <20191029201821.GA26658@localhost>
On 29/10/2019 20:18, Adrian Bunk wrote:
> On Wed, Oct 16, 2019 at 08:44:56AM +1000, Dan Callaghan wrote:
>> Elfutils has optional support for bzip2 and xz (lzma). It uses
>> this for decompressing embedded ELF sections like the .gnu_debugdata
>> section for "mini debuginfo":
>>
>> https://sourceware.org/gdb/onlinedocs/gdb/MiniDebugInfo.html
>> ...
>> +PACKAGECONFIG ??= "bzip2"
>> +PACKAGECONFIG[bzip2] = "--with-bzlib,--without-bzlib,${DEPENDS_BZIP2}"
>> +PACKAGECONFIG[xz] = "--with-lzma,--without-lzma,xz"
>> ...
>
> Is any tooling actually doing this compression by default?
>
> It is a bit surprising that this has the mostly-obsolete bzip2 enabled
> by default but not the more common (and better compressing) xz.
Exactly.
Ross
next prev parent reply other threads:[~2019-10-29 20:51 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
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 [this message]
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=ea2156a7-8f39-ffdc-55ca-6488b115eb2b@intel.com \
--to=ross.burton@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox