Emerge of tar-1.26-r1 on x86 says (with FEATURES="test"): * QA Notice: Automake "maintainer mode" detected: * * /bin/sh /boot/tmp/portage/app-arch/tar-1.26-r1/work/tar-1.26/build-aux/m +issing --run autom4te --language=autotest -I . testsuite.at -o testsuite.tmp * * If you patch Makefile.am, configure.in, or configure.ac then you * should use autotools.eclass and eautomake or eautoreconf. Exceptions * are limited to system packages for which it is impossible to run * autotools during stage building. See * http://www.gentoo.org/proj/en/qa/autofailure.xml for more information. Reproducible: Always
Same problem here. This issue is not present on =app-arch/tar-1.26, so this is a regression. All arches affected.
works fine for me. you must post a full build log as an attachment and `emerge --info` in every bug report like all the documentation says to.
Created attachment 347490 [details] emerge --info tar
Created attachment 347492 [details] build.log
Created attachment 347494 [details] auto*.out, aclocal.out
The automake output complains about stuff there: configure.ac:241: warning: The 'AM_PROG_MKDIR_P' macro is deprecated, and will soon be removed. configure.ac:241: You should use the Autoconf-provided 'AC_PROG_MKDIR_P' macro instead, configure.ac:241: and use '$(MKDIR_P)' instead of '$(mkdir_p)'in your Makefile.am files. lib/Makefile.am:29: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') rmt/Makefile.am:7: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') src/Makefile.am:48: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') tests/Makefile.am:208: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') This is not the "maintainer mode" the QA notice talks about, is it? If not, I'll probably open another bug for this - things like that "<something> will soon be removed" should be printed out in an ewarn, I think.
for some reason on your system, autom4te was passed through the missing helper. for most people, it gets run directly, and that doesn't trigger the portage QA check. make[2]: Entering directory '/var/tmp/portage/app-arch/tar-1.26-r1/work/tar-1.26/tests' autom4te --language=autotest -I . testsuite.at -o testsuite.tmp mv testsuite.tmp testsuite make[2]: Leaving directory '/var/tmp/portage/app-arch/tar-1.26-r1/work/tar-1.26/tests' that said, tar-1.27 already has this issue fixed and is on track for stable in bug 496212.
