From: Harry Putnam <reader@newsguy.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] libsxlt and aclocal/autoconf failing during emerge
Date: Sat, 31 Oct 2009 20:03:27 -0500 [thread overview]
Message-ID: <87fx8znjj4.fsf@newsguy.com> (raw)
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 !";
next reply other threads:[~2009-11-01 1:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-01 1:03 Harry Putnam [this message]
2009-11-01 1:55 ` [gentoo-user] Re: libsxlt and aclocal/autoconf failing during emerge walt
2009-11-01 2:05 ` Harry Putnam
2009-11-01 2:39 ` walt
2009-11-01 3:11 ` Dale
2009-11-01 15:15 ` Harry Putnam
2009-11-01 16:21 ` walt
2009-11-02 6:17 ` Marc Joliet
2009-11-02 15:46 ` Harry Putnam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fx8znjj4.fsf@newsguy.com \
--to=reader@newsguy.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox