| 1 |
walt wrote: |
| 2 |
> On 10/31/2009 07:05 PM, Harry Putnam wrote: |
| 3 |
> |
| 4 |
>> ... |
| 5 |
>> /var/tmp/portage/dev-libs/libxslt-1.1.26/temp/autoconf.out |
| 6 |
>> ***** autoconf ***** |
| 7 |
>> ***** PWD: /var/tmp/portage/dev-libs/libxslt-1.1.26/work/libxslt-1.1.26 |
| 8 |
>> ***** autoconf |
| 9 |
>> |
| 10 |
>> configure.in:120: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL |
| 11 |
>> If this token and others are legitimate, please use m4_pattern_allow. |
| 12 |
>> See the Autoconf documentation. |
| 13 |
>> configure.in:121: error: possibly undefined macro: AM_PROG_LIBTOOL |
| 14 |
>> |
| 15 |
> |
| 16 |
> If I'm interpreting things correctly (unlikely) those two macros are defined |
| 17 |
> in /usr/share/libtool/libtld/aclocal.m4, which belongs to the libtool package. |
| 18 |
> (On my machine, sys-devel/libtool-2.2.6a). |
| 19 |
> |
| 20 |
> Do you have such a file/package on your machine? |
| 21 |
> |
| 22 |
> |
| 23 |
|
| 24 |
I was reluctant to post but I did a google search and although it |
| 25 |
appeared they were talking about Macs and such, they were talking about |
| 26 |
libtool and (e)make's friends. Could it be that there is a version |
| 27 |
mismatch between those three? Maybe one or two are newer than the others? |
| 28 |
|
| 29 |
I also noticed there were a couple other packages affected, which lead |
| 30 |
me to narrow my search a little more. Seems to be the same thoughts all |
| 31 |
the way around tho. |
| 32 |
|
| 33 |
Dale |
| 34 |
|
| 35 |
:-) :-) |
Archives