From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org, Romain Naour <romain.naour@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/glibc: add upstream patch to fix build error with glibc 2.43
Date: Sun, 31 May 2026 08:20:37 +0200 [thread overview]
Message-ID: <ahvTE6qnCu2M6tp3@windsurf> (raw)
In-Reply-To: <20260501171432.1701736-1-bernd@kuhls.net>
On Fri, May 01, 2026 at 07:14:32PM +0200, Bernd Kuhls wrote:
> Seen with this defconfig
>
> BR2_x86_64=y
> BR2_GCC_VERSION_15_X=y
> BR2_TOOLCHAIN_BUILDROOT_CXX=y
> BR2_PACKAGE_PICOTOOL=y
>
> output/host/x86_64-buildroot-linux-gnu/sysroot/usr/include/bits/struct_mutex.h:35:9:
> error: declaration does not declare anything [-fpermissive]
> 35 | short __unused;
>
> No related autobuilder error was recorded.
> The build error does not occur with glibc-2.42 on the 2026.02.x branch.
>
> The build error was reported to picotool upstream:
> https://github.com/raspberrypi/picotool/issues/300
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
Thanks, applied to master. Do you happen to know why glibc upstream
didn't include this patch in its 2.43 maintenance branch, if it fixes
a bug? Maybe something to report to them?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-05-31 6:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-01 17:14 [Buildroot] [PATCH 1/1] package/glibc: add upstream patch to fix build error with glibc 2.43 Bernd Kuhls
2026-05-31 6:20 ` Thomas Petazzoni via buildroot [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=ahvTE6qnCu2M6tp3@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=romain.naour@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox