public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  Re: libsxlt and aclocal/autoconf failing during emerge
Date: Sat, 31 Oct 2009 21:05:28 -0500	[thread overview]
Message-ID: <87639vngnr.fsf@newsguy.com> (raw)
In-Reply-To: hcippv$575$1@ger.gmane.org

walt <w41ter@gmail.com> writes:

> On 10/31/2009 06:03 PM, Harry Putnam wrote:
>> Can anyone tell from the tail of emerge -vuD system
>> what the trouble is with aclocal/autoconf and libxslt.
>> ...
>>  * Failed Running autoconf !
>>  * 
>>  * Include in your bugreport the contents of:
>>  *   /var/tmp/portage/dev-libs/libxslt-1.1.26/temp/autoconf.out
>
> Chances are that the file cited above will give a hint.
> Does that file contain any error messages?

Sorry, I hoped someone would have had the same problem and just
recognize the tail messages.

/var/tmp/portage/dev-libs/libxslt-1.1.26/temp/autoconf.out
***** autoconf *****
***** PWD: /var/tmp/portage/dev-libs/libxslt-1.1.26/work/libxslt-1.1.26
***** autoconf

  configure.in:120: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
  configure.in:121: error: possibly undefined macro: AM_PROG_LIBTOOL

They don't mean anything to me... do that to you?




  reply	other threads:[~2009-11-01  2:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-01  1:03 [gentoo-user] libsxlt and aclocal/autoconf failing during emerge Harry Putnam
2009-11-01  1:55 ` [gentoo-user] " walt
2009-11-01  2:05   ` Harry Putnam [this message]
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=87639vngnr.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