Hi! After poking around, I guess this is actually a glibc issue and it's probably already fixed by this commit:
jbglaw@lili:/var/cache/git/glibc$ git show
3e5760fcb48528d48deeb60cb885a97bb731160c | head -20
commit 3e5760fcb48528d48deeb60cb885a97bb731160c
Author: Joseph Myers <jos...@codesourcery.com>
Date: Wed Sep 28 20:09:34 2022 +0000
Update _FloatN header support for C++ in GCC 13
GCC 13 adds support for _FloatN and _FloatNx types in C++, so breaking
the installed glibc headers that assume such support is not present.
GCC mostly works around this with fixincludes, but that doesn't help
for building glibc and its tests (glibc doesn't itself contain C++
code, but there's C++ code built for tests). Update glibc's
bits/floatn-common.h and bits/floatn.h headers to handle the GCC 13
support directly.
In general the changes match those made by fixincludes, though I think
the ones in sysdeps/powerpc/bits/floatn.h, where the header tests
__LDBL_MANT_DIG__ == 113 or uses #elif, wouldn't match the existing
fixincludes patterns.
[...]
So this can either be closed or reassigned to glibc, which will have a fix in
2.37 I guess.
Thanks,
Jan-Benedict
--
signature.asc
Description: PGP signature
