Re: stdckdint-h: Work around missing declarations with g++ 15.0.

Hi Paul, Paul Eggert writes: > As the stdckdint.h bug in question is fixed in GCC 15.1, wouldn't it > be better if the Gnulib workaround is used only if the bug is present > (GCC 15.0)? Sorry if I phrased it poorly in my previous messages. But it is not a GCC bug. Apparently the C++26 standard

Re: stdckdint-h: Work around missing declarations with g++ 15.0.

As the stdckdint.h bug in question is fixed in GCC 15.1, wouldn't it be better if the Gnulib workaround is used only if the bug is present (GCC 15.0)?

Re: stdckdint-h: Work around missing declarations with g++ 15.0.

Hi Branden, "G. Branden Robinson" writes: > Thanks for checking the build! I don't have an environment quite that > fresh set up and handy. No problem. If you ever feel like testing it you can always create a Fedora container: $ docker run --rm -t -i fedora:latest $ dnf install gcc

Re: stdckdint-h: Work around missing declarations with g++ 15.0.

Hi Bruno, Bruno Haible writes: > We need to test this manually, since the CI runs on GitHub are not > using the gnulib-tool --with-c++-tests. Ah, for some reason I thought we did. > Successfully tested with Solaris 10 CC, Oracle dev studio 12.6 CC, > AIX 7.1 xlC, MSVC 14. So, all is fine. Tha

Re: stdckdint-h: Work around missing declarations with g++ 15.0.

G. Branden Robinson wrote: > Do you think it would be a good idea to backport these fixes to gnulib's > stable/2025-01 branch? I think that yes, the second patch fits the criteria for stable branches . The next round of st

Re: stdckdint-h: Work around missing declarations with g++ 15.0.

[please CC me on replies] Hi Collin, At 2025-05-19T21:46:08-0700, Collin Funk wrote: > When compiling Groff with GCC/G++ 15.0, I run into this compiler > error: Thanks for checking the build! I don't have an environment quite that fresh set up and handy. [snip stdckdint build failure] > The im

Re: stdckdint-h: Work around missing declarations with g++ 15.0.

Collin Funk wrote: > The immediate fix that comes to mind is using 'g++ -std=gnu23', but > there are 2 issues with this: > > 1. gnulib/m4/std-gnu23.m4 has no code for C++ versions, because no > one interested in C++ has contributed it to Autoconf yet. > 2. Bruno told me that the C++ st

Re: qemu linux-user limitations

On Mai 20 2025, Bruno Haible wrote: > Still, I call it a qemu user-mode limitation, because that's how it > presents itself to the user. Adopting the point of view of the user — > as opposed to the point of view of the implementor — is a technique > for writing more successful software. Lying to