* Running eautoreconf in '/var/tmp/portage/dev-db/mysql-5.1.67-r1/work/mysql' ... * Running libtoolize --install --copy --force --automake ... [ ok ] * Running aclocal ... [ !! ] * Failed Running aclocal ! * * Include in your bugreport the contents of: * * /var/tmp/portage/dev-db/mysql-5.1.67-r1/temp/aclocal.out * ERROR: dev-db/mysql-5.1.67-r1 failed (prepare phase): * Failed Running aclocal ! * * Call stack: * ebuild.sh, line 93: Called src_prepare * environment, line 4317: Called mysql-v2_src_prepare * environment, line 3787: Called mysql-autotools_src_prepare * environment, line 3529: Called eautoreconf * environment, line 1051: Called eaclocal * environment, line 954: Called autotools_run_tool '--at-m4flags' 'aclocal' * environment, line 808: Called die * The specific snippet of code: * die "Failed Running $1 !"; # cat /var/tmp/portage/dev-db/mysql-5.1.67-r1/temp/aclocal.out ***** aclocal ***** ***** PWD: /var/tmp/portage/dev-db/mysql-5.1.67-r1/work/mysql ***** aclocal aclocal-1.13: warning: autoconf input should be named 'configure.ac', not 'configure.in' configure.in:25: error: 'AM_CONFIG_HEADER': this macro is obsolete. You should use the 'AC_CONFIG_HEADERS' macro instead. /usr/share/aclocal-1.13/obsolete-err.m4:12: AM_CONFIG_HEADER is expanded from... configure.in:25: the top level autom4te-2.69: /usr/bin/m4 failed with exit status: 1 aclocal-1.13: error: echo failed with exit status: 1 This one probably belongs in the block list of #468608 but it's not for me to make that call.
I've hit this issue earlier this week while testing some changes to the eclass. As the underlying issue here is that mysql-5.1 is old code that is not going to be updated, I've been thinking if should restrict the autotools versions that support this package or if we should try to keep this working a bit longer by adding to the eclass a rename from configure.in to configure.ac. @mysql: opinions?
(In reply to comment #1) > As the underlying issue here is that mysql-5.1 is old code that is not going > to be updated > > @mysql: > opinions? Are you saying the 5.1 is deprecated by upstream and wont have any bugfixes if found in the future, so we are better of upgrading to 5.5? I don't mind upgrading but remember it wasn't without complications last time and the Gentoo mysql docs still seem focused on 4.x and mentioning nothing later than 5.0... not said as a complaint as I know someone have to set aside his/her free time to do it, but I see no encouragement to get people moving forward here. I mean if 5.5 is backward compatible with 5.5 or require just very little preparation a few words about it in the mysql docs shouldn't be too hard to produce?
(In reply to comment #2) > (In reply to comment #1) > > As the underlying issue here is that mysql-5.1 is old code that is not going > > to be updated > > > > @mysql: > > opinions? > > Are you saying the 5.1 is deprecated by upstream and wont have any bugfixes > if found in the future, so we are better of upgrading to 5.5? As you should be aware, upstream development first moved to the 5.5 branch series and is now targetted at the 5.6 series. The 5.1 branch has got a few important security updates, but no more features in a long time. In any case, I was talking about the work on the autotools based build system that has stopped a very long time ago. Since the 5.5 series, MySQL is using cmake, so I don't believe upstream will do any release to update the build system. > I don't mind upgrading but remember it wasn't without complications last > time and the Gentoo mysql docs still seem focused on 4.x and mentioning > nothing later than 5.0... not said as a complaint as I know someone have to > set aside his/her free time to do it, but I see no encouragement to get > people moving forward here. I mean if 5.5 is backward compatible with 5.5 or > require just very little preparation a few words about it in the mysql docs > shouldn't be too hard to produce? We're planning to start soon the work to get MySQL-5.5 marked stable. We'll see if we can get some updates to the documentation.
dev-db/mysql 5.5 is now stable and 5.1 will soon be masked. If this is still an issue, please upgrade
