I have a similar problem. What I have done (to work out of CVS) is have the newer versions of the autotools export from CVS, run autogen.sh and then tar up the results and ship that.
I think for the time being that is a reasonable solution to people w/ older versions of autotools for whatever reason. (In my case, it's because I have to support RHEL 4 vintage systems.) --Mark Alex Myltsev wrote: > On 7/17/07, Ralf S. Engelschall <[EMAIL PROTECTED]> wrote: >> So, in short: if you ever wanted to give RPM 5 a try, I think _NOW_ >> is the first time you can do this in a reasonable way > Is there a possiblity that we could make it work with somewhat older > autotools? > > I have the following versions of the tools: > m4 (GNU M4) 1.4.7 > autoconf (GNU Autoconf) 2.59 > automake (GNU automake) 1.9.6 > libtoolize (GNU libtool) 1.5.22 > gettextize (GNU gettext-tools) 0.14.6 > > and running autoconf on the configure.ac from HEAD spews the following: > > configure.ac:1: error: possibly undefined macro: dnl > If this token and others are legitimate, please use m4_pattern_allow. > See the Autoconf documentation. > configure.ac:16: error: possibly undefined macro: AC_REQUIRE_AUX_FILE > configure.ac:18: error: possibly undefined macro: AM_MAINTAINER_MODE > configure.ac:56: error: possibly undefined macro: AC_PROG_LIBTOOL > configure.ac:354: error: possibly undefined macro: AM_C_PROTOTYPES > configure.ac:387: error: possibly undefined macro: AC_CHECK_LIB > configure.ac:433: error: possibly undefined macro: AC_LINK_IFELSE > configure.ac:752: error: possibly undefined macro: m4_defn > configure:15990: error: possibly undefined macro: m4_foreach_w > configure:15993: error: possibly undefined macro: AC_LANG_CALL > configure:16133: error: possibly undefined macro: AC_MSG_VERBOSE ______________________________________________________________________ RPM Package Manager http://rpm5.org Developer Communication List rpm-devel@rpm5.org
