From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: [Buildroot] [PATCH 0/2] Bump glibc to 2.41
Date: Mon, 3 Feb 2025 22:51:50 +0100 [thread overview]
Message-ID: <20250203215155.1175999-1-thomas.petazzoni@bootlin.com> (raw)
Hello,
glibc 2.41 was released recently, and we want to give a try to have it
in 2025.02, so now is the good time to do the version bump.
While doing the bump, we noticed that a few IGNORE_CVES entries had
become irrelevant, which is solved by PATCH 1/2.
The bump itself is mostly boring, with just a minor tweak to a patch
against localedef.
A quick read of the glibc 2.41 release notes doesn't really show
anything that would cause major breakage, but of course the devil is
in the details, and only an autobuilder pass on this stuff will tell
us.
Thomas
Thomas Petazzoni (2):
package/glibc: drop bogus IGNORE_CVES entries
package/{glibc,localedef}: bump to version 2.41
package/glibc/glibc.hash | 2 +-
package/glibc/glibc.mk | 15 ++-------------
...01-HACK-only-build-and-install-localedef.patch | 10 +++++-----
...dency-on-GCC-to-4.8-and-binutils-to-2.24.patch | 10 +++++-----
...SOC23_SOURCE-undefined-to-build-localede.patch | 14 ++++++++------
package/localedef/localedef.mk | 2 +-
6 files changed, 22 insertions(+), 31 deletions(-)
--
2.48.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2025-02-03 21:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 21:51 Thomas Petazzoni via buildroot [this message]
2025-02-03 21:51 ` [Buildroot] [PATCH 1/2] package/glibc: drop bogus IGNORE_CVES entries Thomas Petazzoni via buildroot
2025-02-04 11:29 ` Peter Korsgaard
2025-02-07 19:41 ` Peter Korsgaard
2025-02-03 21:51 ` [Buildroot] [PATCH 2/2] package/{glibc, localedef}: bump to version 2.41 Thomas Petazzoni via buildroot
2025-02-04 11:29 ` Peter Korsgaard
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=20250203215155.1175999-1-thomas.petazzoni@bootlin.com \
--to=buildroot@buildroot.org \
--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.