When I try to emerge libgamin I get the following: > emerge -v libgamin These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] dev-libs/libgamin-0.1.10-r2 USE="python -debug" 0 kB Total: 1 package (1 new), Size of downloads: 0 kB >>> Verifying ebuild manifests >>> Emerging (1 of 1) dev-libs/libgamin-0.1.10-r2 * gamin-0.1.10.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ] * gamin-0.1.9-freebsd.patch.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking gamin-0.1.9-freebsd.patch.bz2 to /var/tmp/portage/dev-libs/libgamin-0.1.10-r2/work >>> Unpacking gamin-0.1.10.tar.gz to /var/tmp/portage/dev-libs/libgamin-0.1.10-r2/work >>> Source unpacked in /var/tmp/portage/dev-libs/libgamin-0.1.10-r2/work >>> Preparing source in /var/tmp/portage/dev-libs/libgamin-0.1.10-r2/work/gamin-0.1.10 ... * Applying libgamin-0.1.10-compilewarnings.patch ... [ ok ] * Applying gamin-0.1.9-freebsd.patch.bz2 ... [ ok ] * Applying libgamin-0.1.10-noinst-lib.patch ... [ ok ] * Running eautoreconf in '/var/tmp/portage/dev-libs/libgamin-0.1.10-r2/work/gamin-0.1.10' ... * Running aclocal ... [ ok ] * Running autoconf ... [ !! ] * Failed Running autoconf ! * * Include in your bugreport the contents of: * * /var/tmp/portage/dev-libs/libgamin-0.1.10-r2/temp/autoconf.out * * ERROR: dev-libs/libgamin-0.1.10-r2 failed. * Call stack: * ebuild.sh, line 49: Called src_prepare * environment, line 3705: Called eautoreconf * environment, line 1048: Called eautoconf * environment, line 990: Called autotools_run_tool 'autoconf' * environment, line 528: Called die * The specific snippet of code: * die "Failed Running $1 !"; * The die message: * Failed Running autoconf ! * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/dev-libs/libgamin-0.1.10-r2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-libs/libgamin-0.1.10-r2/temp/environment'. * >>> Failed to emerge dev-libs/libgamin-0.1.10-r2, Log file: >>> '/var/tmp/portage/dev-libs/libgamin-0.1.10-r2/temp/build.log' * Messages for package dev-libs/libgamin-0.1.10-r2: * Failed Running autoconf ! * * Include in your bugreport the contents of: * * /var/tmp/portage/dev-libs/libgamin-0.1.10-r2/temp/autoconf.out * * ERROR: dev-libs/libgamin-0.1.10-r2 failed. * Call stack: * ebuild.sh, line 49: Called src_prepare * environment, line 3705: Called eautoreconf * environment, line 1048: Called eautoconf * environment, line 990: Called autotools_run_tool 'autoconf' * environment, line 528: Called die * The specific snippet of code: * die "Failed Running $1 !"; * The die message: * Failed Running autoconf ! * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/dev-libs/libgamin-0.1.10-r2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-libs/libgamin-0.1.10-r2/temp/environment'. * > cat /var/tmp/portage/dev-libs/libgamin-0.1.10-r2/temp/autoconf.out ***** autoconf ***** ***** PWD: /var/tmp/portage/dev-libs/libgamin-0.1.10-r2/work/gamin-0.1.10 ***** autoconf configure.in:30: error: possibly undefined macro: AM_PROG_LIBTOOL If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. The same happens for libsoup: > cat /var/tmp/portage/net-libs/libsoup-gnome-2.26.3-r1/temp/autoconf.out ***** autoconf ***** ***** PWD: /var/tmp/portage/net-libs/libsoup-gnome-2.26.3-r1/work/libsoup-2.26.3 ***** autoconf configure.in:73: error: possibly undefined macro: AM_PROG_LIBTOOL If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. I have the following packages: - autoconf-2.63-r1 - m4-1.4.12 - automake-1.10.2 Reproducible: Always
Everything is fine again after I switched back from libtool-2.2.6a to libtool-1.5.26.
Please run revdep-rebuild & all when migrating to libtool-2. This macro is still there in libtool-2 so this failure should not happen. $ egrep "AM_PROG_LIBTOOL" /usr/share/aclocal* -r /usr/share/aclocal/libtool.m4:AU_ALIAS([AM_PROG_LIBTOOL], [LT_INIT]) /usr/share/aclocal/libtool.m4:dnl AC_DEFUN([AM_PROG_LIBTOOL], [])
Please follow the instructions in comment #2 and get back to us (and reopen this bug). Thanks.
