207114 2008-01-23 02:59 0000 gnome-base/gconf-2.20-r1 fails to build with automake-1.10.1 2008-01-26 13:49:44 0000 1 1 1 Unclassified Gentoo Linux GNOME unspecified All Linux RESOLVED FIXED P2 normal --- 1 covracer@gmail.com gnome@gentoo.org aballier@gentoo.org EckosGentoo@gmail.com lordcris@yahoo.it njdoyle+bugs@gmail.com transacid@centerim.org covracer@gmail.com 2008-01-23 02:59:33 0000 When attempting to emerge gconf-2.20.1-r1, automake --add-missing --copy fails with the following message in automake-*.out: ***** automake ***** configure.in:8: version mismatch. This is Automake 1.10.1, configure.in:8: but the definition used by this AM_INIT_AUTOMAKE configure.in:8: comes from Automake 1.10. You should recreate configure.in:8: aclocal.m4 with aclocal and run autmake again. njdoyle+bugs@gmail.com 2008-01-23 14:45:20 0000 I can confirm to having the same problem. tom111@gmx.de 2008-01-23 15:14:29 0000 I can confirm this bug and additionally it is introduced by =automake-1.10-r1 Downgrading to =automake-1.10 solves the problem. aballier@gentoo.org 2008-01-25 13:32:58 0000 it already uses eautoreconf, it just copies aclocal.m4 and use it. Imho it's not a good idea, better would be to ship missing m4's as a separate tarball or convince upstream to ship them in the tarball (in order to not need any non stricly necessary deps to regenerate the autofoo scripts) removing the line 'cp aclocal.m4 old.m4' fixes this error. flameeyes@gentoo.org 2008-01-25 17:47:16 0000 Gilles, copying aclocal is the worst and stupidest thing ever you could think of. Really. remi@gentoo.org 2008-01-26 09:31:44 0000 *** Bug 207525 has been marked as a duplicate of this bug. *** eva@gentoo.org 2008-01-26 13:49:44 0000 fixed, thanks for reporting