On 11/01/2009 07:15 AM, Harry Putnam wrote: > walt <w41...@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)
