From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/1] package/libdeflate: bump version to 1.26
Date: Sun, 20 Sep 2026 13:41:54 +0200 [thread overview]
Message-ID: <aq_GSgAvnToyCcvQ@windsurf> (raw)
In-Reply-To: <20260920060133.4184-1-bernd@kuhls.net>
On Sun, Sep 20, 2026 at 08:01:33AM +0200, Bernd Kuhls wrote:
> https://github.com/ebiggers/libdeflate/blob/v1.26/NEWS.md
>
> Switched to sha256 tarball hash provided by upstream.
>
> Depends on gcc >= 4.8 because "libdeflate now requires a C11 compiler":
> https://github.com/ebiggers/libdeflate/commit/a7cbb2258188cd459e436b0c0a1e4b892e2b1ac7
C11...
> diff --git a/package/libdeflate/Config.in b/package/libdeflate/Config.in
> index d2fb0d6c55..b8f452e601 100644
> --- a/package/libdeflate/Config.in
> +++ b/package/libdeflate/Config.in
> @@ -1,7 +1,11 @@
> config BR2_PACKAGE_LIBDEFLATE
> bool "libdeflate"
> + depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_8 # C++11
or C++11 ?
According to https://gcc.gnu.org/wiki/C11Status, C11 support was added
in gcc 4.7. Not sure that it matters that much though, these are
really ancient compilers, so I'd be fine with the 4.8 dependency.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-09-20 11:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 6:01 [Buildroot] [PATCH v2 1/1] package/libdeflate: bump version to 1.26 Bernd Kuhls
2026-09-20 11:41 ` Thomas Petazzoni via buildroot [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=aq_GSgAvnToyCcvQ@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox