I found that the configure.in in recent releases of PCRE uses some autoconf macros that won't work unless aclocal is called first to produce a proper aclocal.m4: AC_PROG_LIBTOOL and AC_LIBTOOL_WIN32_DLL

This buildconf patch fixes it for me (and works with both the new PCRE 5.0 and the old version that's currently in the httpd-2.1 tree).

Before I commit it, though, does anyone know of a system where it's not safe to assume aclocal exists?

Thanks,
Brian

Index: buildconf
===================================================================
--- buildconf   (revision 106561)
+++ buildconf   (working copy)
@@ -85,6 +85,7 @@
touch .deps
rm -f aclocal.m4
rm -f generated_lists
+rm -f srclib/pcre/aclocal.m4

# Remove autoconf 2.5x cache directories
rm -rf autom4te*.cache srclib/pcre/autom4te*.cache
@@ -137,7 +138,7 @@
fi

echo rebuilding $pcre_configure
-(cd srclib/pcre && ${AUTOCONF:-autoconf})
+(cd srclib/pcre && ${ACLOCAL:-aclocal} && ${AUTOCONF:-autoconf})

echo rebuilding $config_h_in
rm -f $config_h_in



Reply via email to