Paul Eggert writes: > A better fix is to use AC_C_PROTOTYPES; it's designed for this > purpose. But AC_C_PROTOTYPES futzes with $CC in order to enable > prototypes if available, and there are some chicken-and-egg problems > here since it assumes we've already found a C compiler and yet now we > want to use this test to find a C compiler.
This is fixed in 2.54. The futzing with $CC is now done in AC_PROG_CC. Calling AC_C_PROTOTYPES at random points in your configure.in should be safe. -- Peter Eisentraut [EMAIL PROTECTED]
