The current development version of autoconf seems create
broken configure scripts in certain cases.  Below is an
example of how to reproduce the problem.  I haven't managed
to debug the problem yet -- I am no m4 or autom4te wizard...

Is this a known problem?

Jens


% cat configure.ac
AC_INIT
AC_PROG_CC

AC_CHECK_LIB(z, gzsetparams,
  AC_CHECK_HEADER(zlib.h,,
    AC_MSG_ERROR(zlib headers not found)),
  AC_MSG_ERROR(zlib library not found))

AC_OUTPUT(Makefile)
% touch Makefile.am
% autoreconf
autoconf: warning: -A is obsolete, use --include
autoconf: warning: -l is obsolete, use --include
autoconf: warning: -A is obsolete, use --include
autoconf: warning: -l is obsolete, use --include
% ./configure
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for executable suffix... 
checking for object suffix... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gzsetparams in -lz... yes
./configure: line 1878: syntax error near unexpected token `done'
./configure: line 1878: `done'


If one includes "AC_PROG_CPP" as well, it terminates instead
with:

checking how to run the C preprocessor... gcc -E
checking for gzsetparams in -lz... yes
./configure: line 2664: syntax error near unexpected token `yes:no'
./configure: line 2664: `  yes:no'


Reply via email to