After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 132523 - ./configure: line 1333: syntax error near unexpected token `config.h'
./configure: line 1333: syntax error near unexpected token `config.h'
Status: VERIFIED DUPLICATE of bug 132513
Product: libxml2
Classification: Platform
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: Daniel Veillard
libxml QA maintainers
Depends on:
Blocks:
 
 
Reported: 2004-01-26 05:46 UTC by Daniel Cardenas
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6



Description Daniel Cardenas 2004-01-26 05:46:11 UTC
when invoking jhbuild I receive the following errors:

pen24ghzlinux:~# bin/jhbuild
*** Checking out libxml2 *** [1/85]
 
cvs -z3 -q -d :pserver:anonymous@anoncvs.gnome.org:/cvs/gnome update -dP -A .
*** Configuring libxml2 *** [1/85]
 
./autogen.sh --prefix /opt/gnome2
You should add the contents of `/usr/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
aclocal: configure.in: 43: macro `AM_PROG_LIBTOOL' not found in library
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: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.
/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:44: WITH_PYTHON does not appear in AM_CONDITIONAL
./configure: line 1333: syntax error near unexpected token `config.h'
./configure: line 1333: `AM_CONFIG_HEADER(config.h)'
 
Now type 'make' to compile libxml.
*** Building libxml2 *** [1/85]
 
make
make: *** No targets specified and no makefile found.  Stop.
*** error during stage build of libxml2: could not build module *** [1/85]
 
 
  [1] rerun stage build
  [2] ignore error and continue to install
  [3] give up on module
  [4] start shell
  [5] go to stage force_checkout
  [6] go to stage configure

Daniel Cardenas
Comment 1 James Henstridge 2004-01-28 14:27:16 UTC
Reassigning to libxml2.

Looks like libxml2's autogen.sh script just calls "aclocal" and
"automake", when it should be specifying the version it wants.  Seens
to have some problems if automake 1.8 is installed.
Comment 2 John Fleck 2004-01-28 14:34:07 UTC
This appears to be repaired by the fix in #132513. Marking it as a
dup. Somebody please reopen if I'm wrong.

*** This bug has been marked as a duplicate of 132513 ***
Comment 3 Daniel Veillard 2004-02-12 17:43:16 UTC
This should be closed by release 2.6.6,

  thanks,

Daniel