* Package: net-im/mcabber-0.10.2  * Repository: gentoo  * Maintainer: wschlich@gentoo.org net-im@gentoo.org  * USE: amd64 aspell elibc_glibc kernel_linux modules multilib ssl userland_GNU  * FEATURES: sandbox >>> Unpacking source... >>> Unpacking mcabber-0.10.2.tar.bz2 to /var/tmp/portage/net-im/mcabber-0.10.2/work >>> Source unpacked in /var/tmp/portage/net-im/mcabber-0.10.2/work >>> Preparing source in /var/tmp/portage/net-im/mcabber-0.10.2/work/mcabber-0.10.2 ... * Running eautoreconf in '/var/tmp/portage/net-im/mcabber-0.10.2/work/mcabber-0.10.2' ... * Running libtoolize --install --copy --force --automake ...  [ ok ] * Running aclocal -I macros ...  [ ok ] * Running autoconf ...  [ !! ] * Failed Running autoconf ! * * Include in your bugreport the contents of: * * /var/tmp/portage/net-im/mcabber-0.10.2/temp/autoconf.out * ERROR: net-im/mcabber-0.10.2 failed (prepare phase): * Failed Running autoconf ! * * Call stack: * ebuild.sh, line 93: Called src_prepare * environment, line 3190: Called eautoreconf * environment, line 937: Called eautoconf * environment, line 860: Called autotools_run_tool '--at-m4flags' 'autoconf' * environment, line 705: Called die * The specific snippet of code: * die "Failed Running $1 !"; * * If you need support, post the output of `emerge --info '=net-im/mcabber-0.10.2'`, * the complete build log and the output of `emerge -pqv '=net-im/mcabber-0.10.2'`. /usr/lib64/portage/bin/isolated-functions.sh: line 215: wait: `Failed Running autoconf !': not a pid or valid job spec * The complete build log is located at '/var/tmp/portage/net-im/mcabber-0.10.2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/net-im/mcabber-0.10.2/temp/environment'. * Working directory: '/var/tmp/portage/net-im/mcabber-0.10.2/work/mcabber-0.10.2' * S: '/var/tmp/portage/net-im/mcabber-0.10.2/work/mcabber-0.10.2'