Actually, I've been thinking more of AC_MSG_ERROR itself. It would also hint developers of ac-macros (think of ac-archive) to remember to push checkpoints and extended diagnostics into the config.log itself, and so to keep the user output short and clean. Well, it might be that it was not intended that user macros do send messages to the config.log, wasn't it? Atleast it looks that way...
Es schrieb Akim Demaille: > > checking build system type... i686-pc-linux-gnu > checking host system type... i686-pc-linux-gnu > checking target system type... i686-pc-linux-gnu > checking for gcc... gcc > checking for C compiler default output... configure: error: C compiler cannot create >executables > check config.log for details > > Thanks, I'm installing this: >[...] > [echo "$as_me: failed program was:" >&AS_MESSAGE_LOG_FD > cat conftest.$ac_ext >&AS_MESSAGE_LOG_FD > -AC_MSG_ERROR([_AC_LANG compiler cannot create executables], 77)]) > +AC_MSG_ERROR([_AC_LANG compiler cannot create executables > +check `config.log' for details.], 77)]) > ac_exeext=$ac_cv_exeext > AC_MSG_RESULT([$ac_file]) > ])# _AC_COMPILER_EXEEXT_DEFAULT
