From: Yegor Yefremov via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Cc: Shubham Chakraborty <chakrabortyshubham66@gmail.com>,
"Ernesto L . Williams Jr" <realcontrols@gmail.com>
Subject: [Buildroot] [PATCH 0/2] package/szip: replace with libaec
Date: Tue, 6 Oct 2026 13:07:12 +0200 [thread overview]
Message-ID: <20261006110714.3242851-1-yegorslists@gmail.com> (raw)
From: Yegor Yefremov <yegorslists@googlemail.com>
szip fails to build with GCC >= 15 on non-glibc toolchains, see
https://autobuild.buildroot.org/results/5e400d0e13480c58e8b1b0178bf7e5537dd31751
Instead of keeping it alive with compiler flags, this series replaces
it with libaec. szip has no public repository and its last release
is 2.1.1, while libaec is maintained, BSD licensed, recommended by the
HDF Group, and ships libsz, a drop-in replacement with the same API
(szlib.h) and soname (libsz.so.2). Debian, Fedora, Alpine and Arch
already provide libsz from libaec.
The legacy option for szip selects libaec, so existing configurations
keep a libsz.
This supersedes "[v2] package/szip: fix build with GCC 15":
https://patchwork.buildroot.org/project/buildroot/patch/20260810181422.10955-1-chakrabortyshubham66@gmail.com/
libaec was tested with utils/test-pkg on the default toolchain set
(6 builds, all OK, including noMMU and static).
Yegor Yefremov (2):
package/libaec: new package
package/szip: remove package
Config.in.legacy | 9 +++++++++
DEVELOPERS | 4 +---
package/Config.in | 2 +-
package/libaec/Config.in | 10 ++++++++++
package/libaec/libaec.hash | 3 +++
package/libaec/libaec.mk | 19 +++++++++++++++++++
package/szip/Config.in | 16 ----------------
package/szip/szip.hash | 3 ---
package/szip/szip.mk | 13 -------------
9 files changed, 43 insertions(+), 36 deletions(-)
create mode 100644 package/libaec/Config.in
create mode 100644 package/libaec/libaec.hash
create mode 100644 package/libaec/libaec.mk
delete mode 100644 package/szip/Config.in
delete mode 100644 package/szip/szip.hash
delete mode 100644 package/szip/szip.mk
--
2.34.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-10-06 11:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 11:07 Yegor Yefremov via buildroot [this message]
2026-10-06 11:07 ` [Buildroot] [PATCH 1/2] package/libaec: new package Yegor Yefremov via buildroot
2026-10-06 11:07 ` [Buildroot] [PATCH 2/2] package/szip: remove package Yegor Yefremov via buildroot
2026-10-11 7:07 ` [Buildroot] [PATCH 0/2] package/szip: replace with libaec Thomas Petazzoni via buildroot
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=20261006110714.3242851-1-yegorslists@gmail.com \
--to=buildroot@buildroot.org \
--cc=chakrabortyshubham66@gmail.com \
--cc=realcontrols@gmail.com \
--cc=yegorslists@googlemail.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