[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: echo "enhancement" leads to confused legacy script tools...

From: Henrik Nordstrom
Subject: Re: echo "enhancement" leads to confused legacy script tools...
Date: Mon, 20 Mar 2006 03:53:56 +0100

sön 2006-03-19 klockan 18:04 -0800 skrev Paul Eggert:

>    export CVSROOT=':pserver:address@hidden:/squid'
>    cvs login
>    cvs co squid3
>    cd squid3
>    ./bootstrap.sh


> but this failed as follows:
>    automake : 
>    autoconfg: 
>    libtool  : 
>    Bootstrapping 
>    configure.in:33: error: possibly undefined macro: AC_DISABLE_SHARED
>          If this token and others are legitimate, please use m4_pattern_allow.
>          See the Autoconf documentation.
>    configure.in:34: error: possibly undefined macro: AC_PROG_LIBTOOL
>    configure.in:35: error: possibly undefined macro: AC_LTDL_DLLIB

All of the above is libtool related. Seems your aclocal is not picking
up the libtool macros proper. Seen this on a few systems where the tools
have been versioned a bit too much without proper fallback.. (FreeBSD
ports had this issue).

I don't remember the exact workaround now, but it was along the lines of
adding the autoconf macro repository directory where libtool has
deposited it's macros to the search path index used by aclocal.

From looking at a couple of systems memory begins to clear.. libtool
installs it's macros in share/aclocal/, while aclocal 1.9.6 for some
reason only looks in share/aclocal-1.9/ when automake is installed

Workaround: add /path/to/share/aclocal in share/aclocal-1.9/dirlist, and
complain to the automake package maintainer.. Or if you know another
solution please tell me.

> I am using Autoconf 2.59 (Debian stable), Libtool 1.5.22, and Automake
> 1.9.6.

Bootstraps fine here with the same versions, but on Fedora Core.. 


Attachment: signature.asc
Description: Detta är en digitalt signerad meddelandedel

reply via email to

[Prev in Thread] Current Thread [Next in Thread]