as in summary libabw should depend explicitly on automake:1.14 or ebuild changed to use eautoreconf to be able to find automake version correctly. Reproducible: Always Steps to Reproduce: 1. make sure no automake:1.14 installed (or remove) 2. emerge app-text/libabw 3. notice failure 4. emerge -1 automake:1.14 5 emerge app-text/libabw successful Actual Results: WARNING: 'automake-1.14' is missing on your system. You should only need it if you modified 'Makefile.am' or 'configure.ac' or m4 files included by 'configure.ac'. The 'automake' program is part of the GNU Automake package: <http://www.gnu.org/software/automake> It also requires GNU Autoconf, GNU m4 and Perl in order to run: <http://www.gnu.org/software/autoconf> <http://www.gnu.org/software/m4/> <http://www.perl.org/> Makefile:414: recipe for target 'Makefile.in' failed make[3]: *** [Makefile.in] Error 127 make[3]: Leaving directory '/var/tmp/portage/app-text/libabw-0.1.1/work/libabw-0.1.1/src/lib' Makefile:371: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/var/tmp/portage/app-text/libabw-0.1.1/work/libabw-0.1.1/src' Makefile:482: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/var/tmp/portage/app-text/libabw-0.1.1/work/libabw-0.1.1' Makefile:392: recipe for target 'all' failed make: *** [all] Error 2 * ERROR: app-text/libabw-0.1.1::gentoo failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=app-text/libabw-0.1.1::gentoo'`, * the complete build log and the output of `emerge -pqv '=app-text/libabw-0.1.1::gentoo'`. * The complete build log is located at '/var/tmp/portage/app-text/libabw-0.1.1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-text/libabw-0.1.1/temp/environment'. * Working directory: '/var/tmp/portage/app-text/libabw-0.1.1/work/libabw-0.1.1' * S: '/var/tmp/portage/app-text/libabw-0.1.1/work/libabw-0.1.1' >>> Failed to emerge app-text/libabw-0.1.1, Log file: >>> '/var/tmp/portage/app-text/libabw-0.1.1/temp/build.log' * Messages for package app-text/libabw-0.1.1: * ERROR: app-text/libabw-0.1.1::gentoo failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=app-text/libabw-0.1.1::gentoo'`, * the complete build log and the output of `emerge -pqv '=app-text/libabw-0.1.1::gentoo'`. * The complete build log is located at '/var/tmp/portage/app-text/libabw-0.1.1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-text/libabw-0.1.1/temp/environment'. * Working directory: '/var/tmp/portage/app-text/libabw-0.1.1/work/libabw-0.1.1' * S: '/var/tmp/portage/app-text/libabw-0.1.1/work/libabw-0.1.1' * * The following package has failed to build, install, or execute postinst: * * (app-text/libabw-0.1.1:0/0::gentoo, ebuild scheduled for merge), Log file: * '/var/tmp/portage/app-text/libabw-0.1.1/temp/build.log'
Created attachment 429636 [details] build.log
same with amd64
libabw-0.1.1-boost-1.59.patch changes src/lib/Makefile.am, but eautoreconf is missing.
eautoreconf fixing this.
Created attachment 429766 [details] diff
base eclass inherit seems deprecated. simple eautoreconf in src_prepare sufficient.
It would be best to bump straight to EAPI=6 here, drop base.eclass and just run default in src_prepare instead.
whatever FIXES this. boost patch touching Makefile.am, obvious fix is to run eautoreconf, either explicitly in older EAPI or automatically, if this what newer EAPI have implemented.
Default src_prepare() in EAPI 6 is applying patches from ${PATCHES}, but is not calling eautoreconf. So something like the following could be used in EAPI 6: src_prepare() { default eautoreconf }
Thanks for the report, fixed per https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=dba07d4f6c3c0c691e2a0e6eda57accbf88dc245
