While upgrading vte from version 0.16.6-r1 to 0.16.8 emerge ends up running automake. Reproducible: Always Steps to Reproduce: 1.emerge -v vte Actual Results: * Running aclocal ... [ ok ] * Running libtoolize --copy --force --automake ... [ ok ] * Running aclocal ... [ ok ] * Running autoconf ... [ ok ] * Running autoheader ... [ ok ] * Running automake --add-missing --copy ... [ !! ] * Failed Running automake ! * * Include in your bugreport the contents of: * * /var/tmp/portage/x11-libs/vte-0.16.8/temp/automake-18256.out * * ERROR: x11-libs/vte-0.16.8 failed. * Call stack: * ebuild.sh, line 1654: Called dyn_unpack * ebuild.sh, line 768: Called qa_call 'src_unpack' * ebuild.sh, line 44: Called src_unpack * vte-0.16.8.ebuild, line 54: Called eautoreconf * autotools.eclass, line 97: Called eautomake * autotools.eclass, line 194: Called autotools_run_tool 'automake' '--add-missing' '--copy' * autotools.eclass, line 218: Called die * * Failed Running automake ! * 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/x11-libs/vte-0.16.8/temp/build.log'. Contents of /var/tmp/portage/x11-libs/vte-0.16.8/temp/build.log: ***** automake ***** gtk-doc.make:7: GTK_DOC_USE_LIBTOOL does not appear in AM_CONDITIONAL doc/reference/Makefile.am:63: `gtk-doc.make' included from here gtk-doc.make:43: ENABLE_GTK_DOC does not appear in AM_CONDITIONAL doc/reference/Makefile.am:63: `gtk-doc.make' included from here gtk-doc.make:136: ENABLE_GTK_DOC does not appear in AM_CONDITIONAL doc/reference/Makefile.am:63: `gtk-doc.make' included from here src/Makefile.am:310: compiling `buffer.c' with per-target flags requires `AM_PROG_CC_C_O' in `configure.in' Makefile.am:13: shell echo $(PACKAGE: non-POSIX variable name Makefile.am:13: (probably a GNU make extension) Installed versions of automake: sys-devel/automake-1.10 sys-devel/automake-1.4_p6 sys-devel/automake-1.5 sys-devel/automake-1.6.3 sys-devel/automake-1.7.9-r1 sys-devel/automake-1.8.5-r3 sys-devel/automake-1.9.6-r2
confirmed, same versions of automake running here, same error.
Additionally the ChangeLog claims that it uses python-config to determine python location and this probably can't work with our current python2.4 provided python-config. Therefore I have package.masked this until the mess is fixed.
I just unmasked a fixed version of this ebuild. Could you please try it ? (the ebuild is in CVS since yesterday but I unmasked it this morning)
(In reply to comment #3) > I just unmasked a fixed version of this ebuild. Could you please try it ? > (the ebuild is in CVS since yesterday but I unmasked it this morning) > Builds ok, thanks.
python-config is bug 188029
actually automake doesn't suffer from this problem it seems, anyway thanks all for the reports.
(In reply to comment #2) > Additionally the ChangeLog claims that it uses python-config to determine > python location and this probably can't work with our current python2.4 > provided python-config. > Therefore I have package.masked this until the mess is fixed. > see bug #189770
