Bug 207114 - gnome-base/gconf-2.20-r1 fails to build with automake-1.10.1
|
Bug#:
207114
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: gnome@gentoo.org
|
Reported By: covracer@gmail.com
|
|
Component: GNOME
|
|
|
URL:
|
|
Summary: gnome-base/gconf-2.20-r1 fails to build with automake-1.10.1
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2008-01-23 02:59 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.
I can confirm to having the same problem.
I can confirm this bug and additionally it is introduced by =automake-1.10-r1
Downgrading to =automake-1.10 solves the problem.
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.
Gilles, copying aclocal is the worst and stupidest thing ever you could think
of. Really.
*** Bug 207525 has been marked as a duplicate of this bug. ***
fixed, thanks for reporting
