FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo User

 
 
LinkBack Thread Tools
 
Old 11-01-2009, 12:03 AM
Harry Putnam
 
Default libsxlt and aclocal/autoconf failing during emerge

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 !";
 
Old 11-01-2009, 12:55 AM
walt
 
Default libsxlt and aclocal/autoconf failing during emerge

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?
 
Old 11-01-2009, 01:05 AM
Harry Putnam
 
Default libsxlt and aclocal/autoconf failing during emerge

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?
 
Old 11-01-2009, 01:39 AM
walt
 
Default libsxlt and aclocal/autoconf failing during emerge

On 10/31/2009 07:05 PM, Harry Putnam wrote:
> ...
> /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

If I'm interpreting things correctly (unlikely) those two macros are defined
in /usr/share/libtool/libtld/aclocal.m4, which belongs to the libtool package.
(On my machine, sys-devel/libtool-2.2.6a).

Do you have such a file/package on your machine?
 
Old 11-01-2009, 02:11 AM
Dale
 
Default libsxlt and aclocal/autoconf failing during emerge

walt wrote:
> On 10/31/2009 07:05 PM, Harry Putnam wrote:
>
>> ...
>> /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
>>
>
> If I'm interpreting things correctly (unlikely) those two macros are defined
> in /usr/share/libtool/libtld/aclocal.m4, which belongs to the libtool package.
> (On my machine, sys-devel/libtool-2.2.6a).
>
> Do you have such a file/package on your machine?
>
>

I was reluctant to post but I did a google search and although it
appeared they were talking about Macs and such, they were talking about
libtool and (e)make's friends. Could it be that there is a version
mismatch between those three? Maybe one or two are newer than the others?

I also noticed there were a couple other packages affected, which lead
me to narrow my search a little more. Seems to be the same thoughts all
the way around tho.

Dale

:-) :-)
 
Old 11-01-2009, 02:15 PM
Harry Putnam
 
Default libsxlt and aclocal/autoconf failing during emerge

walt <w41ter@gmail.com> writes:

> On 10/31/2009 07:05 PM, Harry Putnam wrote:
>> ...
>> /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
>
> If I'm interpreting things correctly (unlikely) those two macros are defined
> in /usr/share/libtool/libtld/aclocal.m4, which belongs to the libtool package.
> (On my machine, sys-devel/libtool-2.2.6a).
>
> Do you have such a file/package on your machine?

I have libtool installed but not that new of version. In fact portage
doesn't show that new a version being available for ~x86, as of this
mornings sync.. (Its masked here)

reader > eix sys-devel/libtool
[i] sys-devel/libtool
Available versions:
(1.3) 1.3.5
(1.5) 1.5.26 (~)1.5.26-r1 [m]2.2.6a [m]**9999
{test vanilla}
Installed versions: 1.5.26-r1(1.5)(14:09:44 10/31/09)
Homepage: http://www.gnu.org/software/libtool/
Description: A shared library tool for developers
 
Old 11-01-2009, 03:21 PM
walt
 
Default libsxlt and aclocal/autoconf failing during emerge

On 11/01/2009 07:15 AM, Harry Putnam wrote:
> walt <w41ter@gmail.com> writes:
>
>> On 10/31/2009 07:05 PM, Harry Putnam wrote:
>>> ...
>>> /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
>>
>> If I'm interpreting things correctly (unlikely) those two macros are defined
>> in /usr/share/libtool/libtld/aclocal.m4, which belongs to the libtool package.
>> (On my machine, sys-devel/libtool-2.2.6a).
>>
>> Do you have such a file/package on your machine?
>
> I have libtool installed but not that new of version. In fact portage
> doesn't show that new a version being available for ~x86, as of this
> mornings sync.. (Its masked here)

Hm, yes, that's odd.

Well, when in doubt, blame libtool anyway. It's a bet you'll win most of
the time. Get out the shotgun and run lafilefixer --justfixit (install
lafilefixer if you don't already have it).

You might want to run fix_libtool_files also if you've upgraded gcc lately.

If that doesn't work, reinstall libtool.

If that doesn't work, emerge -C libtool ;o)
 
Old 11-02-2009, 05:17 AM
Marc Joliet
 
Default libsxlt and aclocal/autoconf failing during emerge

Am Sun, 01 Nov 2009 09:15:29 -0600
schrieb Harry Putnam <reader@newsguy.com>:

> walt <w41ter@gmail.com> writes:
>
> > On 10/31/2009 07:05 PM, Harry Putnam wrote:
> >> ...
> >> /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
> >
> > If I'm interpreting things correctly (unlikely) those two macros are defined
> > in /usr/share/libtool/libtld/aclocal.m4, which belongs to the libtool package.
> > (On my machine, sys-devel/libtool-2.2.6a).
> >
> > Do you have such a file/package on your machine?
>
> I have libtool installed but not that new of version. In fact portage
> doesn't show that new a version being available for ~x86, as of this
> mornings sync.. (Its masked here)
>
> reader > eix sys-devel/libtool
> [i] sys-devel/libtool
> Available versions:
> (1.3) 1.3.5
> (1.5) 1.5.26 (~)1.5.26-r1 [m]2.2.6a [m]**9999
> {test vanilla}
> Installed versions: 1.5.26-r1(1.5)(14:09:44 10/31/09)
> Homepage: http://www.gnu.org/software/libtool/
> Description: A shared library tool for developers

Wait, but those are small 'm's. That means they must have been masked
manually. As Alan McKinnon mentioned in your other thread ("When masked pkg not
in [...]profiles/package.mask, where is it"), you might have an entry
in /etc/portage/package.mask.

HTH
--
Marc Joliet
--
Lt. Frank Drebin: "It's true what they say: cops and women don't mix. Like
eating a spoonful of Drāno; sure, it'll clean you out, but it'll leave you
hollow inside."
 
Old 11-02-2009, 02:46 PM
Harry Putnam
 
Default libsxlt and aclocal/autoconf failing during emerge

Marc Joliet <marcec@gmx.de> writes:

> Wait, but those are small 'm's. That means they must have been masked
> manually. As Alan McKinnon mentioned in your other thread ("When masked pkg not
> in [...]profiles/package.mask, where is it"), you might have an entry
> in /etc/portage/package.mask.

My god... I'm really losing it. I masked it apparently but don't
remember it.
 

Thread Tools




All times are GMT. The time now is 11:18 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org