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

2025-05-21 Thread Collin Funk
Hi Bruno, Bruno Haible writes: > I agree that when the system has a working implementation of a .h file, > we should interfere with it to the least possible amount. > > But the problem here is > 1) The term "working implementation" depends on the language in effect. > It may be working C

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

2025-05-21 Thread Paul Eggert
On 5/21/25 14:44, Bruno Haible wrote: I would therefore propose a more future-proof approach: based on the same approach as we have been taken for so many other .h files. Yes that all should work. All I'm saying is that if that approach determines that the system is fine (for both C and C++,

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

2025-05-21 Thread Bruno Haible via Gnulib discussion list
Paul Eggert wrote: > > we have no way of portably setting the compiler flags > > if available. > > That's fine, but Gnulib does have a portable way to see whether the C++ > compiler works properly with . Namely, compile a little > test with the C++ compiler and if that compiles OK, do not > ge

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

2025-05-21 Thread Collin Funk
Bruno Haible via Gnulib discussion list writes: > Paul Eggert wrote: >> 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)? > > Who said that is was fixed in GCC 15.1 ? I reproduce it with g

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

2025-05-21 Thread Bruno Haible via Gnulib discussion list
Paul Eggert wrote: > 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)? Who said that is was fixed in GCC 15.1 ? I reproduce it with groff HEAD and gnulib HEAD~2 and GCC 15.1.0 (built from sou

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

2025-05-21 Thread Collin Funk
Paul Eggert writes: > That's fine, but Gnulib does have a portable way to see whether the > C++ compiler works properly with . Namely, compile a > little test with the C++ compiler and if that compiles > OK, do not generate stdckdint.h. > > In general we're better off if we don't second-guess a

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

2025-05-21 Thread Paul Eggert
On 2025-05-20 19:33, Collin Funk wrote: we have no way of portably setting the compiler flags if available. That's fine, but Gnulib does have a portable way to see whether the C++ compiler works properly with . Namely, compile a little test with the C++ compiler and if that compiles OK, do