From 52d9a3c34f4dbc6e9372d87a357efeb7fd6ce1ae Mon Sep 17 00:00:00 2001
From: Yang Tse <yangsita@gmail.com>
Date: Tue, 29 Jul 2008 02:26:21 +0000
Subject: 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.
---
 ares/buildconf | 8 --------
 1 file changed, 8 deletions(-)

(limited to 'ares/buildconf')

diff --git a/ares/buildconf b/ares/buildconf
index bfaf39e87..364d5a06e 100755
--- a/ares/buildconf
+++ b/ares/buildconf
@@ -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}
-- 
cgit v1.2.3