* Bruce Korb wrote on Mon, Apr 30, 2007 at 12:04:53AM CEST: > The index and search of the docs only yields this: > > `AM_PROG_CC_C_O' > This is like `AC_PROG_CC_C_O', but it generates its results in the > manner required by automake. You must use this instead of > `AC_PROG_CC_C_O' when you need this functionality, that is, when > using per-target flags or subdir-objects with C sources. The above is from the Automake manual. AC_PROG_CC_C_O is explained in the Autoconf manual (the name prefix hints to where this macro comes from): | -- Macro: AC_PROG_CC_C_O | If the C compiler does not accept the `-c' and `-o' options | simultaneously, define `NO_MINUS_C_MINUS_O'. This macro actually | tests both the compiler found by `AC_PROG_CC', and, if different, | the first `cc' in the path. The test fails if one fails. This | macro was created for GNU Make to choose the default C compilation | rule. Hope that helps. Cheers, Ralf _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
