Sergio Durigan Junior wrote: > the specific case of the command line invocation, here's what is being > used: > > gcc -DHAVE_CONFIG_H -I. -I../../../../binutils-gdb/gdb/gnulib/import -I.. > -g -D_GLIBCXX_DEBUG -MT glob.o -MD -MP -MF $depbase.Tpo -c -o glob.o > ../../../../binutils-gdb/gdb/gnulib/import/glob.c &&\ > mv -f $depbase.Tpo $depbase.Po
So, it's using 'gcc' without any '-std=...' option. By [1] it is probably a gcc version 4.8.x. By [2] it uses -std=gnu90 by default. This explains the error messages at least. So it boils down to what Paul hinted at: Why was the 'c99' module not effective? For this, it would be good if you could attach config.log (config.status and config.cache are not sufficient for analyzing this). Bruno [1] https://github.com/linux-on-ibm-z/docs/wiki/Building-GCC-4.8 [2] https://gcc.gnu.org/onlinedocs/gcc-4.8.5/gcc/Standards.html
