aclocal.out shows: ***** aclocal ***** ***** PWD: /var/tmp/portage/gnome-extra/gnome-power-manager-2.29.91/work/gnome-power-manager-2.29.91 ***** aclocal -I m4 configure.ac:365: warning: underquoted definition of AC_CHECK_X_HEADER configure.ac:365: run info '(automake)Extending aclocal' configure.ac:365: or see http://sources.redhat.com/automake/automake.html#Extending-aclocal configure.ac:1: error: Autoconf version 2.65 or higher is required configure.ac:1: the top level autom4te-2.63: /usr/bin/m4 failed with exit status: 63 aclocal-1.10: autom4te failed with exit status: 63 Upgrading autoconf to 2.65 and autoconf-wrapper to 8 solves the issue. Reproducible: Always Steps to Reproduce:
those are current ~arch release. What did you expect from the overlay, really ? @base-system, could you advise on if we should use WANT_AUTOCONF (currently that wouldn't allow selection of 2.65 though) for this or adding the build-dep manually ?
(In reply to comment #1) > those are current ~arch release. What did you expect from the overlay, really ? to add autoconf-2.65 and autoconf-wrapper-8 to dep, please.
The autoconf-2.65 dependency was added in commit 55e69bf800fc8d18290560b549f85bb3638fb143 Author: Richard Hughes <richard@hughsie.com> Date: Tue Jan 26 18:16:24 2010 +0000 trivial: Modernize the configure.ac file :100644 100644 9b70f1d7393b219176c01a2d1338f372baa844eb de83dd2cca4b3c34101f9ce9f6a6928e359cc3ea M configure.ac
we could probably extend WANT_AUTOCONF handling in autotools.eclass so that it forced a newer DEPEND for packages that need it
Still valid for g-p-m-2.30 from the overlay
*** Bug 312795 has been marked as a duplicate of this bug. ***
I've just hit the same problem with gnome-power-manager 2.30.1, evidently the overlay ebuild didn't check for dependency on autoconf > 2.65. It would be nice to have that sorted.
sys-devel/autoconf-2.65 is stable on most arches ( bug 311967 ), so i'm closing this as resolved. Please reopen or pm me if you think that this issue isn't resolved.
*** Bug 330961 has been marked as a duplicate of this bug. ***