From: Ross Burton <ross.burton@intel.com>
To: Dan Callaghan <dan.callaghan@opengear.com>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v3] elfutils: add PACKAGECONFIG for compression algorithms
Date: Wed, 30 Oct 2019 23:05:58 +0000 [thread overview]
Message-ID: <dd047b35-85bc-e238-48b3-1edae5c8dc00@intel.com> (raw)
In-Reply-To: <1572385232-sup-1496@galangal.danc.bne.opengear.com>
On 29/10/2019 21:46, Dan Callaghan wrote:
> I couldn't find anything that would ever use the bzip2 decompression in
> elfutils, so I had a quick look at why they even added bzip2 support in
> the first place. It turns out it was for reading compressed kernel
> images (presumably, in the elfutils tools like eu-readelf):
>
> https://sourceware.org/git/?p=elfutils.git;a=commitdiff;h=d6ccdc1a05f27bf0bb5d802ec14f879aa9fe3e98
>
> commit d6ccdc1a05f27bf0bb5d802ec14f879aa9fe3e98
> Author: Roland McGrath <roland@redhat.com>
> Date: Wed Aug 26 00:23:01 2009 -0700
>
> libdwfl: Support Linux bzip2 kernel images for automatic decompression.
>
> And indeed on my Fedora host eu-readelf can decode ELF information from
> a kernel bzImage, but the eu-readelf built by Yocto's elfutils-native
> recipe says "not a valid ELF file" when I feed it the same bzImage.
>
> Whether that's useful or not is a different question. In our product
> I am planning to disable bzip2 (because we don't use the elfutils tools
> for anything) and enable xz (for .gnu_debugdata sections).
Good digging, thanks.
Lets default to bzip being off for now, and then if anyone does want
this then they can just turn it on.
Ross
next prev parent reply other threads:[~2019-10-30 23:06 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
2019-10-29 21:46 ` Dan Callaghan
2019-10-30 23:05 ` Ross Burton [this message]
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=dd047b35-85bc-e238-48b3-1edae5c8dc00@intel.com \
--to=ross.burton@intel.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox