Re[3]: AC_PROG_CXX does not work correctly after AC_PROG_CC

[Laurynas Biveinis]

> My suggestion would probably be to
>   a) have the EXEEXT tests fail graciously (i.e. have them
>      give a 'warning: cannot determine executable extension
>      using the <LANG> compiler', and not set any findings (so
>      possible following AC_PROG_<COMPILER> calls can find it
>      out properly).

Why? EXEEXT works like a sanity check for a compiler.  As I understand
it, it bombs only if it cannot find an executable made by compiler.

>   b) have the AC_PROG_<compiler> either bomb out if the
>      requested compiler is not available, or set the respective
>      variable to 'none', so scripts can decide what to do.

I've seen in mailing list archives that this feature (making checks
optionals by user) was already considered couple of years ago,
however, there are still no signs of actual implementation.

Laurynas