GNOME Bugzilla – Bug 129861
CVS HEAD fails to build with automake-1.8 and aclocal-1.8
Last modified: 2009-08-15 18:40:50 UTC
Checking out jhbuild, running jhbuild bootstrap (and saying yes to everything), and then running jhbuild results in the following errors while trying to configure libxml2 (sorry for pasting everything; I'm not sure what the most relevant part is): ./autogen.sh --prefix /opt/gnome2 --disable-static --disable-gtk-doc You should add the contents of `/opt/gnome2/share/aclocal/libtool.m4' to `aclocal.m4'. acinclude.m4:4: warning: underquoted definition of AC_TRY_EVAL2 run info '(automake)Extending aclocal' or see http://sources.redhat.com/automake/automake.html#Extending%20aclocal acinclude.m4:9: warning: underquoted definition of AC_TRY_COMPILE2 /opt/gnome2/share/aclocal/pkg.m4:5: warning: underquoted definition of PKG_CHECK_MODULES /opt/gnome2/share/aclocal/audiofile.m4:12: warning: underquoted definition of AM_PATH_AUDIOFILE /opt/gnome2/share/aclocal/pkg.m4:5: warning: underquoted definition of PKG_CHECK_MODULES /opt/gnome2/share/aclocal/audiofile.m4:12: warning: underquoted definition of AM_PATH_AUDIOFILE /opt/gnome2/share/aclocal/libtool.m4:2510: error: m4_defn: undefined macro: _m4_divert_diversion /opt/gnome2/share/aclocal/libtool.m4:5805: _LT_AC_TAGVAR is expanded from... /opt/gnome2/share/aclocal/libtool.m4:2510: the top level autom4te: /usr/bin/m4 failed with exit status: 1 aclocal: autom4te failed with exit status: 1 configure.in: no proper invocation of AM_INIT_AUTOMAKE was found. configure.in: You should verify that configure.in invokes AM_INIT_AUTOMAKE, configure.in: that aclocal.m4 is present in the top-level directory, configure.in: and that aclocal.m4 was recently regenerated (using aclocal). Makefile.am:22: WITH_TRIO_SOURCES does not appear in AM_CONDITIONAL Makefile.am: installing `./COPYING' Makefile.am:17: Libtool library used but `LIBTOOL' is undefined Makefile.am:17: Makefile.am:17: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' Makefile.am:17: to `configure.in' and run `aclocal' and `autoconf' again. Makefile.am: installing `./depcomp' /opt/gnome2/share/automake-1.8/am/depend2.am: am__fastdepCC does not appear in AM_CONDITIONAL /opt/gnome2/share/automake-1.8/am/depend2.am: AMDEP does not appear in AM_CONDITIONAL /opt/gnome2/share/automake-1.8/am/depend2.am: am__fastdepCC does not appear in AM_CONDITIONAL /opt/gnome2/share/automake-1.8/am/depend2.am: AMDEP does not appear in AM_CONDITIONAL /opt/gnome2/share/automake-1.8/am/depend2.am: am__fastdepCC does not appear in AM_CONDITIONAL /opt/gnome2/share/automake-1.8/am/depend2.am: AMDEP does not appear in AM_CONDITIONAL python/Makefile.am:28: WITH_PYTHON does not appear in AM_CONDITIONAL python/Makefile.am:34: Libtool library used but `LIBTOOL' is undefined python/Makefile.am:34: python/Makefile.am:34: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' python/Makefile.am:34: to `configure.in' and run `aclocal' and `autoconf' again./opt/gnome2/share/automake-1.8/am/depend2.am: am__fastdepCC does not appear in AM_CONDITIONAL /opt/gnome2/share/automake-1.8/am/depend2.am: AMDEP does not appear in AM_CONDITIONAL python/tests/Makefile.am:43: WITH_PYTHON does not appear in AM_CONDITIONAL configure.in:4: error: possibly undefined macro: AM_CONFIG_HEADER If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.in:25: error: possibly undefined macro: AM_INIT_AUTOMAKE configure.in:39: error: possibly undefined macro: AM_C_PROTOTYPES configure.in:42: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL configure.in:43: error: possibly undefined macro: AM_PROG_LIBTOOL configure.in:187: error: possibly undefined macro: AC_TRY_COMPILE2 configure.in:192: error: possibly undefined macro: AC_MSG_RESULT configure.in:208: error: possibly undefined macro: AC_MSG_WARN configure.in:388: error: possibly undefined macro: AM_CONDITIONAL ./configure: line 1333: syntax error near unexpected token `config.h' ./configure: line 1333: `AM_CONFIG_HEADER(config.h)' However, going to /opt/gnome2/bin/ and running 'chmod a-rx *1.8*' (so that aclocal-1.8 and automake-1.8 are no longer readable or executable) and then rerunning the configuration stage fixes this problem.
bug blocks development and testing, so I'm setting priority to immediate. I'm also adding the bugsquad keyword.
Well I don't see how this related to libxml2 itself. Maybe automake-1.8 MUST NOt be used if it's not compatible with previous versions. If you have a working patch provide it, but otherwise I tend to think it's not my problem, you seems to have a lot of errors from automake, related to various m4 not from libxml2, so don't use automake-1.7 if it breaks everything ! Daniel
Seems a fix for this has been submitted, and will close this problem. Daniel *** This bug has been marked as a duplicate of 132513 ***
This should be closed by release 2.6.6, thanks, Daniel