From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Sergey Matyukevich <geomatsi@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH v2] package/elfutils: enable zstd support for host package
Date: Sun, 09 Feb 2025 08:47:49 +0100 [thread overview]
Message-ID: <874j13a7a2.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20250205162034.3be981f5@windsurf> (Thomas Petazzoni via buildroot's message of "Wed, 5 Feb 2025 16:20:34 +0100")
>>>>> "Thomas" == Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:
> On Sat, 7 Dec 2024 23:28:52 +0300
> Sergey Matyukevich <geomatsi@gmail.com> wrote:
>> Buildroot fails to build Linux kernel configurations where BTF support
>> is enabled together with zstd compression of debugging information.
>> The reason is in host-elfutils zstd support being explicitly disabled.
>> So enable zstd support in host-elfutils by default to fix such builds.
>>
>> Signed-off-by: Sergey Matyukevich <geomatsi@gmail.com>
>> ---
> Applied to master, thanks. I'm not a big fan of unconditionally adding
> zstd support, as it adds build time, but we don't really have a simple
> good way to make it optional, and other compression algos are already
> unconditionally enabled.
Committed to 2024.02.x and 2024.11.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-02-09 7:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-07 20:28 [Buildroot] [PATCH v2] package/elfutils: enable zstd support for host package Sergey Matyukevich
2025-02-05 15:20 ` Thomas Petazzoni via buildroot
2025-02-09 7:47 ` Peter Korsgaard [this message]
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=874j13a7a2.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=geomatsi@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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.