diff options
author | Yang Tse <yangsita@gmail.com> | 2008-07-29 02:26:21 +0000 |
---|---|---|
committer | Yang Tse <yangsita@gmail.com> | 2008-07-29 02:26:21 +0000 |
commit | d20656e947f124db5a44c00ae9ed9e23f0af38f3 (patch) | |
tree | 21180721920719e14854ff082564ff62a0ace0a3 /buildconf | |
parent | d79fe5cde049749bfc556256d73da90672fff547 (diff) | |
download | c-ares-d20656e947f124db5a44c00ae9ed9e23f0af38f3.tar.gz c-ares-d20656e947f124db5a44c00ae9ed9e23f0af38f3.tar.bz2 c-ares-d20656e947f124db5a44c00ae9ed9e23f0af38f3.zip |
Tests done using 'aclocal -I m4' in buildconf and 'ACLOCAL_AMFLAGS = -I m4
in top Makefile.am triggered a problem that prevented aclocal from running
successfully on SunOS 5.10 with GNU m4 1.4.5 and GNU Autoconf 2.61
A tarball which reproduces mentioned problem is the one dated July-28-2008
http://cool.haxx.se/curl-daily/curl-7.19.0-20080728.tar.gz
We actually don't need all the bells and whistles that the above mechanism
provides. We only need to include our m4/reentrant.m4 file in acinclude.m4
so here we go with this simpler mechanism.
Diffstat (limited to 'buildconf')
-rwxr-xr-x | buildconf | 8 |
1 files changed, 0 insertions, 8 deletions
@@ -1,13 +1,5 @@ #!/bin/sh -if test -z "$ACLOCAL_FLAGS"; then - ACLOCAL_FLAGS="-I m4" -else - ACLOCAL_FLAGS="$ACLOCAL_FLAGS -I m4" -fi -export ACLOCAL_FLAGS -echo "cares buildconf: using ACLOCAL_FLAGS: $ACLOCAL_FLAGS" - ${LIBTOOLIZE:-libtoolize} --copy --automake --force ${ACLOCAL:-aclocal} $ACLOCAL_FLAGS ${AUTOHEADER:-autoheader} |