Re: Help understanding AC_TRY_CPP

[Akim Demaille <akim at epita dot fr>]

>>>>> "Earnie" == Earnie Boyd <earnie_boyd@yahoo.com> writes:

Earnie> config.log doesn't contain the compilers failure if I remember
Earnie> correctly.  Only where in configure that it is.

Hm, what do you mean?

/tmp % cat configure.in
AC_INIT
AC_PROG_CC
AC_TRY_COMPILE([int main () { syntax error}])
/tmp % ~ace/autoconf -m ~ace        
/tmp % ./configure && cat config.log
loading cache ./config.cache
checking for gcc... gcc
checking whether the C compiler (gcc   ) works... yes
checking whether the C compiler (gcc   ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

configure:593: checking for gcc
configure:718: checking whether the C compiler (gcc   ) works
configure:734: gcc -o conftest    conftest.c  1>&5
configure:760: checking whether the C compiler (gcc   ) is a cross-compiler
configure:765: checking whether we are using GNU C
configure:774: gcc -E conftest.c
configure:792: checking whether gcc accepts -g
configure:834: gcc -c -g -O2  conftest.c 1>&5
configure: In function `main':
configure:824: `syntax' undeclared (first use in this function)
configure:824: (Each undeclared identifier is reported only once
configure:824: for each function it appears in.)
configure:824: parse error before `error'
configure: At top level:
configure:827: redefinition of `main'
configure:824: `main' previously defined here
configure: failed program was:
#line 823 "configure"
#include "confdefs.h"
int main () { syntax error}
int
main ()
{

  ;
  return 0;
}