Karl Berry wrote: > [Limiting to gnulib] > > + - Don't use the flags -std=c99 or -std=gnu99. > > This is not a realistic option as far as I can tell.
There are three ways out. Yes, in some cases, one or the other is unrealistic, and the user will have to consider the other ones. The best we can do is to list the available ways out. > As the user, I never specified -std=gnu99. coreutils and/or gnulib and/or > gcc "helpfully" inserted it somewhere, somehow. Most likely it was the AC_PROG_CC_STDC invocation in coreutils/configure.ac. coreutils needs some C99 features (mixing declarations and statements in a block, which gcc supports already by default) but does not need the C99 semantics of 'inline'; yet, it is the latter which causes trouble with the old glibc headers. If only it was possible to ask the AC_PROG_CC_STDC macro to turn on C99 support only for non-GCC compilers... Bruno
