Follow-up Comment #5, sr #111243 (group autoconf):

[comment #4 comment #4:]
>> I cannot reproduce the problem with stdbool.h using Autoconf 2.72 (as
>> shipped with Fedora 42), when building cifs-tools commit
>> 5ba5b16a73e70b586355b591f9feefbe3c493bc2 (aka version 7.3).
> 
> Hm, that's interesting.  And I'm assuming that you're using GCC 15 as well?
Yes, Fedora 42 currently uses gcc (GCC) 15.1.1 20250425 (Red Hat 15.1.1-1).

> I just checked and the build is indeed using Autoconf 2.72, so it wasn't a
> mistake on my end.
I don't see how that's possible, given that the diagnostic says just "checking
for stdbool.h that conforms to C99". You can check this by creating a file
'configure.ac' in a fresh directory, with the following contents:

AC_INIT([minimal], [1.0], [nob...@nowhere.com])
AC_CHECK_HEADER_STDBOOL
AC_OUTPUT

Then run these shell commands:

autoconf
./configure

The output should be something like the following. If not, that suggests a
problem in your setup somewhere.

checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for _Bool... yes
checking for stdbool.h that conforms to C99 or later... yes
configure: creating ./config.status

Notice that the penultimate line ends "to C99 or later... yes" not "to C99"
without the "or later" as was in your original bug report. That's a dead
giveaway that you were not using Autoconf 2.72.



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/support/?111243>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

Attachment: signature.asc
Description: PGP signature

Reply via email to