>>> Emerging (1 of 5) app-arch/tar-1.26-r1 * tar-1.26.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking tar-1.26.tar.bz2 to /var/tmp/portage/app-arch/tar-1.26-r1/work >>> Source unpacked in /var/tmp/portage/app-arch/tar-1.26-r1/work >>> Preparing source in /var/tmp/portage/app-arch/tar-1.26-r1/work/tar-1.26 ... * Applying tar-1.26-xattr.patch ... [ ok ] * Applying tar-1.26-no-gets.patch ... [ ok ] * Running eautoreconf in '/var/tmp/portage/app-arch/tar-1.26-r1/work/tar-1.26' ... * Running autopoint --force ... [ ok ] * Running aclocal -I m4 ... [ ok ] * Running autoconf ... [ ok ] * ERROR: app-arch/tar-1.26-r1 failed (prepare phase): * internal error: add AC_CONFIG_HEADER to ALL_AUTOTOOLS_MACROS * * Call stack: * ebuild.sh, line 93: Called src_prepare * environment, line 3178: Called eautoreconf * environment, line 921: Called eautoheader * environment, line 843: Called _at_uses_autoheader * environment, line 268: Called _at_uses_pkg 'AC_CONFIG_HEADERS' 'AC_CONFIG_HEADER' 'AM_CONFIG_HEADERS' 'AM_CONFIG_HEADER' * environment, line 300: Called autotools_check_macro 'AC_CONFIG_HEADERS' 'AC_CONFIG_HEADER' 'AM_CONFIG_HEADERS' 'AM_CONFIG_HEADER' * environment, line 596: Called die * The specific snippet of code: * has ${macro} ${ALL_AUTOTOOLS_MACROS[@]} || die "internal error: add ${macro} to ALL_AUTOTOOLS_MACROS"; * * If you need support, post the output of `emerge --info '=app-arch/tar-1.26-r1'`, * the complete build log and the output of `emerge -pqv '=app-arch/tar-1.26-r1'`. /usr/lib64/portage/bin/isolated-functions.sh: line 215: wait: `internal error: add AC_CONFIG_HEADER to ALL_AUTOTOOLS_MACROS': not a pid or valid job spec * The complete build log is located at '/var/tmp/portage/app-arch/tar-1.26-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-arch/tar-1.26-r1/temp/environment'. * Working directory: '/var/tmp/portage/app-arch/tar-1.26-r1/work/tar-1.26' * S: '/var/tmp/portage/app-arch/tar-1.26-r1/work/tar-1.26'
*** This bug has been marked as a duplicate of bug 467772 ***
