public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <raj.khem@gmail.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] glibc: Upgrade to 2.43 release
Date: Mon, 23 Feb 2026 10:01:44 +0100	[thread overview]
Message-ID: <DGM7WKPONTXD.ZOV8O0CMQHXR@bootlin.com> (raw)
In-Reply-To: <20260127053941.792825-1-raj.khem@gmail.com>

On Tue Jan 27, 2026 at 6:39 AM CET, Khem Raj via lists.openembedded.org wrote:
> License-Update: Match to changes [1]
>
> Added free_sized, free_aligned_sized, memset_explicit, memalignment, and new time bases (TIME_MONOTONIC, etc.).
>
> Support for the Linux mseal system call to protect memory mappings (sealing).
>
> Added support for the openat2 system call, allowing more granular file opening options.
>
> New, optimized, and correctly rounded functions from the CORE-MATH project (acosh, asinh, atanh, erf, erfc, lgamma, tgamma).
>
> Significant 4x improvements for fused multiply-add (FMA) on AMD Zen 3 by updating ldbl-96 implementation.
>
> Improved remainder, frexp, and frexpl.
>
> Experimental Clang Support: Added support for building with LLVM Clang (version 18+) on AArch64/x86_64 Linux.
>
> New CPU Detection: Enhanced detection for newer CPU architectures.
>
> 64-bit atomics for 32bit x86 patch is no longer required since upstrea has dropped this logic in 2.43 release
>
> [1] https://sourceware.org/git/?p=glibc.git;a=commit;h=a0ce8b0779e290596e99ca6d96c301684a2d7cfe
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---

Hi Khem,

I have some build issue with this patch. Yet I had some merge
conflicts, so maybe my resolutions were not correct.

ERROR: nativesdk-gcc-runtime-15.2.0-r0 do_compile: Execution of '/srv/pokybuild/yocto-worker/genericx86-64/build/build/tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-gcc-runtime/15.2.0/temp/run.do_compile.3275864' failed with exit code 1
...
| /srv/pokybuild/yocto-worker/genericx86-64/build/build/tmp/work-shared/gcc-15.2.0-r0/sources/gcc-15.2.0/libgomp/affinity-fmt.c:330:25: error: initialization discards 'const' qualifier from pointer target type [-Werror=discarded-qualifiers]
|   330 |               char *q = strchr (p + 1, '}');
|       |                         ^~~~~~

https://autobuilder.yoctoproject.org/valkyrie/#/builders/4/builds/3240
https://autobuilder.yoctoproject.org/valkyrie/#/builders/19/builds/3229

The branch that was tested if you want to check: https://git.yoctoproject.org/poky-ci-archive/tag/?h=oecore/autobuilder.yoctoproject.org/valkyrie/a-full-3260

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  parent reply	other threads:[~2026-02-23  9:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-27  5:39 [PATCH] glibc: Upgrade to 2.43 release Khem Raj
2026-01-27 11:40 ` Varatharajan, Deepesh
2026-02-21 14:30   ` [OE-core] " Randy MacLeod
2026-02-23  7:11     ` Mathieu Dubois-Briand
2026-02-23  9:01 ` Mathieu Dubois-Briand [this message]
2026-03-05 16:23   ` Randy MacLeod
2026-03-05 20:29     ` Khem Raj
2026-03-06 18:59       ` Hemanth Kumar M D
2026-03-06 20:05         ` Martin Jansa
2026-03-08 14:28           ` Hemanth Kumar M D

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=DGM7WKPONTXD.ZOV8O0CMQHXR@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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