From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: libc-alpha@sourceware.org,
Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Subject: Re: Freeze for glibc-2.43, machine testing
Date: Mon, 05 Jan 2026 14:12:38 +0100 [thread overview]
Message-ID: <3670756.iIbC2pHGDl@noumea> (raw)
In-Reply-To: <67927f40-4121-4565-9e8d-2000c46e34ed@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 945 bytes --]
>
> Hi Andreas,
>
> Unfortunately I added three blockers related to build issues:
>
Yeah, I've already seen it, thanks... topic for the meeting on monday.
I'll revisit my odd clang results too.
> 1. https://patchwork.sourceware.org/project/glibc/patch/20251229151201.2453737-1-adhemerval.zanella@linaro.org/
> 2. https://patchwork.sourceware.org/project/glibc/patch/20251223173052.2172201-1-adhemerval.zanella@linaro.org/
> 3. https://patchwork.sourceware.org/project/glibc/patch/20251223173109.2172381-1-adhemerval.zanella@linaro.org/
>
> The 1. prevents to bootstrap a full gcc (including libstd++) on x86_64
> due the new __MATH_TG_BUILTIN_CLASSIFY macro being incompatible with
> C++. The 2. and 3. are build issues for -Os.
>
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, comrel, toolchain, base-system, perl, libreoffice)
https://wiki.gentoo.org/wiki/User:Dilfridge
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 870 bytes --]
prev parent reply other threads:[~2026-01-05 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-04 20:53 Andreas K. Huettel
2026-01-05 11:38 ` Adhemerval Zanella Netto
2026-01-05 13:12 ` Andreas K. Huettel [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=3670756.iIbC2pHGDl@noumea \
--to=dilfridge@gentoo.org \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).