From: martin.jansa@gmail.com
To: openembedded-core@lists.openembedded.org
Cc: Michael Halstead <mhalstead@linuxfoundation.org>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: [whinlatter][PATCH 3/9] yocto-uninative: Update to 5.1 for glibc 2.43
Date: Thu, 9 Apr 2026 17:28:22 +0200 [thread overview]
Message-ID: <20260409152839.2894434-3-martin.jansa@gmail.com> (raw)
In-Reply-To: <20260409152839.2894434-1-martin.jansa@gmail.com>
From: Michael Halstead <mhalstead@linuxfoundation.org>
yocto-uninative: Update to 5.1 for glibc 2.43
Signed-off-by: Michael Halstead <mhalstead@linuxfoundation.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
meta/conf/distro/include/yocto-uninative.inc | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/meta/conf/distro/include/yocto-uninative.inc b/meta/conf/distro/include/yocto-uninative.inc
index e9dc6c8640..d97c96f631 100644
--- a/meta/conf/distro/include/yocto-uninative.inc
+++ b/meta/conf/distro/include/yocto-uninative.inc
@@ -6,10 +6,10 @@
# to the distro running on the build machine.
#
-UNINATIVE_MAXGLIBCVERSION = "2.42"
-UNINATIVE_VERSION = "5.0"
+UNINATIVE_MAXGLIBCVERSION = "2.43"
+UNINATIVE_VERSION = "5.1"
UNINATIVE_URL ?= "http://downloads.yoctoproject.org/releases/uninative/${UNINATIVE_VERSION}/"
-UNINATIVE_CHECKSUM[aarch64] ?= "a25f2174d0cefcb22af005e9bc72ac01ae83b011c5b6d6d5bf00dac979877f76"
-UNINATIVE_CHECKSUM[i686] ?= "959cc2539b692f9b9862825c7324a0fe4d061fca742f6c259f67f581c59af956"
-UNINATIVE_CHECKSUM[x86_64] ?= "96045e8b1e242c8a849426a8506c7043f354b39f2bc0035192780e8205e23e9d"
+UNINATIVE_CHECKSUM[aarch64] ?= "4166237a9dabd222dcb9627a9435dffd756764fabf76ed7ef2e93dc2964567ad"
+UNINATIVE_CHECKSUM[i686] ?= "761502cc9aef4d54d0c6fe9418beb9fdd2c6220da6f2b04128c89f47902ab9ae"
+UNINATIVE_CHECKSUM[x86_64] ?= "2b63a078c26535e0786e87f81ae69509df30f4dce40693004c527bd5e4ab2b85"
next prev parent reply other threads:[~2026-04-09 15:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 15:28 [whinlatter][PATCH 1/9] dtc: backport fix for build with glibc-2.43 martin.jansa
2026-04-09 15:28 ` [whinlatter][PATCH 2/9] pseudo: Add fix for glibc 2.43 martin.jansa
2026-04-09 15:28 ` martin.jansa [this message]
2026-04-09 15:28 ` [whinlatter][PATCH 4/9] m4: backport 3 gnulib changes to fix build with glibc-2.43 on host martin.jansa
2026-04-09 15:28 ` [whinlatter][PATCH 5/9] gettext: backport " martin.jansa
2026-04-09 15:28 ` [whinlatter][PATCH 6/9] util-linux: backport fix to " martin.jansa
2026-04-09 15:28 ` [whinlatter][PATCH 7/9] systemd: " martin.jansa
2026-04-09 15:28 ` [whinlatter][PATCH 8/9] gcc: backport a fix for building with gcc-16 martin.jansa
2026-04-09 15:28 ` [whinlatter][PATCH 9/9] binutils: backport patch to fix build with glibc-2.43 on host martin.jansa
2026-04-09 19:17 ` [OE-core] [whinlatter][PATCH 1/9] dtc: backport fix for build with glibc-2.43 Yoann Congal
2026-04-09 21:29 ` Martin Jansa
2026-04-10 7:41 ` Yoann Congal
2026-04-10 9:09 ` Martin Jansa
2026-04-10 9:28 ` Yoann Congal
2026-04-10 9:39 ` Martin Jansa
2026-04-10 9:44 ` Yoann Congal
2026-04-10 10:09 ` Martin Jansa
2026-04-10 9:19 ` Yoann Congal
[not found] ` <18A4CD91CED0CFD1.657799@lists.openembedded.org>
2026-04-10 6:14 ` Martin Jansa
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=20260409152839.2894434-3-martin.jansa@gmail.com \
--to=martin.jansa@gmail.com \
--cc=mhalstead@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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