public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: martin.jansa@gmail.com
To: openembedded-core@lists.openembedded.org
Cc: Michael Halstead <mhalstead@linuxfoundation.org>,
	Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: [scarthgap][PATCH 3/6] meta/conf/distro/include/yocto-uninative.inc
Date: Thu, 26 Mar 2026 19:14:47 +0100	[thread overview]
Message-ID: <20260326181450.1262870-3-martin.jansa@gmail.com> (raw)
In-Reply-To: <20260326181450.1262870-1-martin.jansa@gmail.com>

From: Michael Halstead <mhalstead@linuxfoundation.org>

yocto-uninative: Update to 5.0 for needed patchelf updates

Solves some segfaults on relocated qemu-img binaries.

[YOCTO #16003]

Signed-off-by: Michael Halstead <mhalstead@linuxfoundation.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
 meta/conf/distro/include/yocto-uninative.inc | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/meta/conf/distro/include/yocto-uninative.inc b/meta/conf/distro/include/yocto-uninative.inc
index 3ced03d477..e9dc6c8640 100644
--- a/meta/conf/distro/include/yocto-uninative.inc
+++ b/meta/conf/distro/include/yocto-uninative.inc
@@ -7,9 +7,9 @@
 #
 
 UNINATIVE_MAXGLIBCVERSION = "2.42"
-UNINATIVE_VERSION = "4.9"
+UNINATIVE_VERSION = "5.0"
 
 UNINATIVE_URL ?= "http://downloads.yoctoproject.org/releases/uninative/${UNINATIVE_VERSION}/"
-UNINATIVE_CHECKSUM[aarch64] ?= "812045d826b7fda88944055e8526b95a5a9440bfef608d5b53fd52faab49bf85"
-UNINATIVE_CHECKSUM[i686] ?= "5cc28efd0c15a75de4bcb147c6cce65f1c1c9d442173a220f08427f40a3ffa09"
-UNINATIVE_CHECKSUM[x86_64] ?= "4c03d1ed2b7b4e823aca4a1a23d8f2e322f1770fc10e859adcede5777aff4f3a"
+UNINATIVE_CHECKSUM[aarch64] ?= "a25f2174d0cefcb22af005e9bc72ac01ae83b011c5b6d6d5bf00dac979877f76"
+UNINATIVE_CHECKSUM[i686] ?= "959cc2539b692f9b9862825c7324a0fe4d061fca742f6c259f67f581c59af956"
+UNINATIVE_CHECKSUM[x86_64] ?= "96045e8b1e242c8a849426a8506c7043f354b39f2bc0035192780e8205e23e9d"


  parent reply	other threads:[~2026-03-26 18:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26 18:14 [scarthgap][PATCH 1/6] dtc: backport fix for build with glibc-2.43 martin.jansa
2026-03-26 18:14 ` [scarthgap][PATCH 2/6] pseudo: Add fix for glibc 2.43 martin.jansa
2026-03-26 18:14 ` martin.jansa [this message]
2026-03-26 18:31   ` Patchtest results for [scarthgap][PATCH 3/6] meta/conf/distro/include/yocto-uninative.inc patchtest
2026-03-26 18:14 ` [scarthgap][PATCH 4/6] yocto-uninative: Update to 5.1 for glibc 2.43 martin.jansa
2026-03-26 18:14 ` [scarthgap][PATCH 5/6] elfutils: don't add -Werror to avoid discarded-qualifiers martin.jansa
2026-03-28  0:07   ` [OE-core] " Yoann Congal
2026-03-28  8:37     ` Martin Jansa
     [not found]     ` <18A0F4787AD7D398.263554@lists.openembedded.org>
2026-03-28  8:41       ` Martin Jansa
2026-03-26 18:14 ` [scarthgap][PATCH 6/6] binutils: backport patch to fix build with glibc-2.43 on host martin.jansa
  -- strict thread matches above, loose matches on Subject: below --
2026-04-21  5:42 [scarthgap][PATCH 1/6] dtc: backport fix for build with glibc-2.43 martin.jansa
2026-04-21  5:42 ` [scarthgap][PATCH 3/6] meta/conf/distro/include/yocto-uninative.inc 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=20260326181450.1262870-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