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
Now if I remove all calls to RPM_CHECK_LIB, then autoconf runs
smoothly (modulo some constructions like AC_REQUIRE_AUX_FILE, but that
I can understand and fix). It seems than something inside
RPM_CHECK_LIB breaks dnl and others.
I will continue trying to fix that myself, but any ideas on how to do
this would be greatly appreciated. Upgrading autotools
distribution-wide is a sizable task, so it is not an option right now.
Upgrading m4 to 1.4.10 does not fix the issue.
______________________________________________________________________
RPM Package Manager http://rpm5.org
Developer Communication List [email protected]
