Can anyone tell from the tail of emerge -vuD system what the trouble is with aclocal/autoconf and libxslt.
First it failed on aclocal... I re-emerged emerge -v sys-devel/aclocal-wrapper Tried again and it failed on autoconf emerge -v sys-devel/autoconf-wrapper But that didn't help it ... still fails at autoconf. [...] >>> Preparing source in >>> /var/tmp/portage/dev-libs/libxslt-1.1.26/work/libxslt-1.1.26 ... * Applying libxslt.m4-libxslt-1.1.26.patch ... [ ok ] * Applying libxslt-1.1.23-parallel-install.patch ... [ ok ] * Applying libxslt-1.1.26-undefined.patch ... [ ok ] * Running eautoreconf in '/var/tmp/portage/dev-libs/libxslt-1.1.26/work/libxslt-1.1.26' ... * Running aclocal ... [ ok ] * Running autoconf ... [ !! ] * Failed Running autoconf ! * * Include in your bugreport the contents of: * * /var/tmp/portage/dev-libs/libxslt-1.1.26/temp/autoconf.out * ERROR: dev-libs/libxslt-1.1.26 failed: * Failed Running autoconf ! * * Call stack: * ebuild.sh, line 49: Called src_prepare * environment, line 2797: Called eautoreconf * environment, line 944: Called eautoconf * environment, line 886: Called autotools_run_tool 'autoconf' * environment, line 425: Called die * The specific snippet of code: * die "Failed Running $1 !";
