I am trying to track down a problem with configure scripts generated by
Autoconf 2.52 and 2.53 using configure.in's written for Autoconf 2.13. I
have attached a very short file that gets converted into a configure
script with syntax errors. For example, with Autoconf 2.53 on Linux:
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 suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
./configure: command substitution: line 5: syntax error near unexpected
token `"(c'
./configure: command substitution: line 5: ` echo $ECHO_N "(cached)
$ECHO_C" >&6'
./configure: cleaning: command not found
./configure: line 2058: syntax error near unexpected token `done'
./configure: line 2058: ` done'
Is there something inherently bad with what I am doing in this example?
Or is there some (hopefully very simple) way to fix it such that it will
work with Autoconf 2.13 and 2.5x? The problem I am facing is that I have
written a lot of tests using this idiom, and I don't want to have to
change all of them just so that my configure scripts will work with 2.5x.
-Patrick
--
Patrick L. Hartling | Research Assistant, VRAC
[EMAIL PROTECTED] | 2624 Howe Hall -- (515)294-4916
http://www.137.org/patrick/ | http://www.vrac.iastate.edu/
AC_INIT(some-file)
AC_PROG_CC
AC_CHECK_LIB(m,
AC_CHECK_HEADER(math.h, echo "Hello",
AC_MSG_ERROR(*** Header not found (oops) ***)))
