>>> Unpacking source... >>> Unpacking evince-2.22.0.tar.bz2 to /var/tmp/portage/app-text/evince-2.22.0/work * Fixing OMF Makefiles ...  [ ok ] * Running elibtoolize in: evince-2.22.0 * Applying portage-1.5.10.patch ... * Applying sed-1.5.6.patch ... * Applying evince-0.7.1-display-menu.patch ...  [ ok ] * Applying evince-0.6.1-dbus-switch.patch ...  [ ok ] * Running eautoreconf in '/var/tmp/portage/app-text/evince-2.22.0/work/evince-2.22.0' ... * Running aclocal ...  [ ok ] * Running libtoolize --copy --force --automake ...  [ ok ] * Running aclocal ...  [ ok ] * Running autoconf ...  [ ok ] * Running autoheader ...  [ ok ] * Running automake --add-missing --copy ...  [ !! ] * Failed Running automake ! * * Include in your bugreport the contents of: * * /var/tmp/portage/app-text/evince-2.22.0/temp/automake-25419.out * * ERROR: app-text/evince-2.22.0 failed. * Call stack: * ebuild.sh, line 49: Called src_unpack * environment, line 2799: Called eautoreconf * environment, line 884: Called eautomake * environment, line 858: Called autotools_run_tool 'src_unpack' 'src_unpack' 'automake' * environment, line 378: Called die * The specific snippet of code: * die "Failed Running $1 !"; * The die message: * Failed Running automake ! * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/app-text/evince-2.22.0/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-text/evince-2.22.0/temp/environment'. *