On 02/02/2013 05:13 AM, Michał Górny wrote: > In order to solve that properly, I would like to request having two new > macros in autoconf: AC_PROG_CC_GNU89 and AC_PROG_CC_GNU99, in a similar > manner to the AC_PROG_CC_C99 macro. We've been moving in the opposite direction: AC_PROG_CC_STDC, AC_PROG_CC_C89 and AC_PROG_CC_C99 will be marked as obsolescent in the next version of Autoconf. The idea is that AC_PROG_CC should "just work", and maintainers shouldn't have to fiddle with all those AC_PROG_CC_whatever macros whenever a new compiler comes out. Can you give an example of a package that has a problem, and symptoms of the problem? That might help us come up with a better solution. For example, what happens if you configure with "./configure CC='clang -std=gnu11'"? _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf
