> | I'm having a very strange problem since I upgraded to 2.53 this
morning.
> I have some m4 code that previously worked under autoconf-2.52 but now
it
> fails under 2.53. I'm trying to check for the script cgicc-config in
the
> given path. configure is failing with the message
> | configure: e
| > | AC_DEFUN(CGICC_CHECK_CONFIG, [
| > | AC_PATH_PROG(CGICC_CONFIG, cgicc-config, no, [$1/bin:$PATH])
| > | if test "$CGICC_CONFIG" = no; then
| > | AC_MSG_ERROR(cgicc-config not found in $1/bin:$PATH)
| > | fi
| > |
| > | cgicc_libdir=`$CGICC_CONFIG --libdir`
| > | cgicc_included
> Well, it just happens that you have a problem with something which can
> be named a bug, but it turns out it is also bound to something which
> is a problem in Autoconf. This problem is that we should not use `:'
> in this argument. The reason is that on an architecture such as DOS,
> where th
Below is the what I see with make check.
Making check in bin
make[1]: Entering directory `/usr/zenez/build/osr5/autoconf-2.53/bin'
make[1]: Nothing to be done for `check'.
make[1]: Leaving directory `/usr/zenez/build/osr5/autoconf-2.53/bin'
Making check in tests
make[1]: Entering directory `/usr/
