| 1 |
walt <w41ter@×××××.com> writes: |
| 2 |
|
| 3 |
> On 10/31/2009 06:03 PM, Harry Putnam wrote: |
| 4 |
>> Can anyone tell from the tail of emerge -vuD system |
| 5 |
>> what the trouble is with aclocal/autoconf and libxslt. |
| 6 |
>> ... |
| 7 |
>> * Failed Running autoconf ! |
| 8 |
>> * |
| 9 |
>> * Include in your bugreport the contents of: |
| 10 |
>> * /var/tmp/portage/dev-libs/libxslt-1.1.26/temp/autoconf.out |
| 11 |
> |
| 12 |
> Chances are that the file cited above will give a hint. |
| 13 |
> Does that file contain any error messages? |
| 14 |
|
| 15 |
Sorry, I hoped someone would have had the same problem and just |
| 16 |
recognize the tail messages. |
| 17 |
|
| 18 |
/var/tmp/portage/dev-libs/libxslt-1.1.26/temp/autoconf.out |
| 19 |
***** autoconf ***** |
| 20 |
***** PWD: /var/tmp/portage/dev-libs/libxslt-1.1.26/work/libxslt-1.1.26 |
| 21 |
***** autoconf |
| 22 |
|
| 23 |
configure.in:120: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL |
| 24 |
If this token and others are legitimate, please use m4_pattern_allow. |
| 25 |
See the Autoconf documentation. |
| 26 |
configure.in:121: error: possibly undefined macro: AM_PROG_LIBTOOL |
| 27 |
|
| 28 |
They don't mean anything to me... do that to you? |
Archives