Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Richard Purdie" <richard.purdie@linuxfoundation.org>,
	<raj.khem@gmail.com>
Cc: <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] glibc: Upgrade to 2.42 release
Date: Wed, 06 Aug 2025 17:37:37 +0200	[thread overview]
Message-ID: <DBVGG6SISEDC.3IXT8OM0GUMXS@bootlin.com> (raw)
In-Reply-To: <dc49c5a116ba8f1752daee81b33d04d9ed099d4b.camel@linuxfoundation.org>

On Wed Aug 6, 2025 at 5:20 PM CEST, Richard Purdie wrote:
> On Wed, 2025-08-06 at 07:32 -0700, Khem Raj via lists.openembedded.org
> wrote:
>> On Wed, Aug 6, 2025 at 7:26 AM Mathieu Dubois-Briand
>> <mathieu.dubois-briand@bootlin.com> wrote:
>> > 
>> > On Tue Jul 29, 2025 at 3:29 AM CEST, Khem Raj via
>> > lists.openembedded.org wrote:
>> > > * GCC 12.1 or later is now required to build the GNU C Library.
>> > > * GNU Binutils 2.39 or later is now required to build the GNU C
>> > > Library.
>> > > * Support for lightweight stack guard pages via madvise and the
>> > >   MADV_GUARD_INSTALL flag has been added to pthread_create.
>> > > * This is major release, changelog [1]
>> > > 
>> > > [1]
>> > > https://sourceware.org/pipermail/libc-announce/2025/000048.html
>> > > 
>> > > Signed-off-by: Khem Raj <raj.khem@gmail.com>
>> > > ---
>> > 
>> > Hi Khem,
>> > 
>> > Sorry for the delay on this patch.
>> > 
>> > It looks like buildtools cannot build after this update, because of
>> > ncurses-native:
>> > 
>> > ERROR: ncurses-native-6.5-r0 do_install: oe_runmake failed
>> > ...
>> > > ** Building terminfo database, please wait...
>> > ...
>> > > tic: /srv/pokybuild/yocto-
>> > > worker/buildtools/build/build/tmp/work/x86_64-nativesdk-pokysdk-
>> > > linux/buildtools-extended-tarball/1.0/testimage-sdk/bitbake-
>> > > build-sj26dmh3/tmp/sysroots-uninative/x86_64-linux/lib/libc.so.6:
>> > > version `GLIBC_2.42' not found (required by /srv/pokybuild/yocto-
>> > > worker/buildtools/build/build/tmp/work/x86_64-nativesdk-pokysdk-
>> > > linux/buildtools-extended-tarball/1.0/testimage-sdk/bitbake-
>> > > build-sj26dmh3/tmp/work/x86_64-linux/ncurses-
>> > > native/6.5/build/narrowc/lib/libtinfo.so.5)
>> > > ? tic could not build /srv/pokybuild/yocto-
>> > > worker/buildtools/build/build/tmp/work/x86_64-nativesdk-pokysdk-
>> > > linux/buildtools-extended-tarball/1.0/testimage-sdk/bitbake-
>> > > build-sj26dmh3/tmp/work/x86_64-linux/ncurses-
>> > > native/6.5/image/srv/pokybuild/yocto-
>> > > worker/buildtools/build/build/tmp/work/x86_64-nativesdk-pokysdk-
>> > > linux/buildtools-extended-tarball/1.0/testimage-sdk/bitbake-
>> > > build-sj26dmh3/tmp/work/x86_64-linux/ncurses-native/6.5/recipe-
>> > > sysroot-native/usr/share/terminfo
>> > 
>> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/43/builds/2179
>> > 
>> > Can you have a look at these, please?
>> 
>> Its reporting about glibc 2.42 versioned symbols, so I wonder if we
>> need to have uninative with glibc-2.42 as well before this can build.
>
> That would make sense, I think we'll have to build and release a new
> uninative to resolve this...
>
> Was that the only failure?
>

Yes it is.


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



      reply	other threads:[~2025-08-06 15:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-29  1:29 [PATCH] glibc: Upgrade to 2.42 release Khem Raj
2025-07-29  1:46 ` Patchtest results for " patchtest
2025-08-06 14:26 ` [OE-core] " Mathieu Dubois-Briand
2025-08-06 14:32   ` Khem Raj
2025-08-06 15:20     ` Richard Purdie
2025-08-06 15:37       ` Mathieu Dubois-Briand [this message]

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