Are there any reasons not to merge AC_PROG_CPP into AC_PROG_CC?  I'm
in the process of having the test suite correctly run AC_PROG_CC
before all the tests that need a compiler, that is, I am
AC_LANG_COMPILER_REQUIRE for all the test that compile, link and/or
run.

I still face failures for macros using AC_TRY_CPP which do require
AC_PROG_CPP, but since AC_PROG_CPP does not require AC_PROG_CC it ends
up using ac_cpp='a-broken-cc -E', hence fails.

I see no advantage in keeping the macros separated, and in fact, I'd
like to move the body of AC_PROG_CPP into AC_PROG_CC, and AU_DEFUN
AC_PROG_CPP to nothing.  Would that be wrong?

I suppose the only real question is: are there any packages that use
AC_PROG_CPP but not AC_PROG_CC?  Can it make sense?

        Akim

Reply via email to