bug-autoconf
[Top][All Lists]
Advanced

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

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


From: Ralf Wildenhues
Subject: Re: echo "enhancement" leads to confused legacy script tools...
Date: Mon, 20 Mar 2006 08:33:10 +0100
User-agent: Mutt/1.5.11

* Paul Eggert wrote on Mon, Mar 20, 2006 at 03:04:43AM CET:

> If you can reproduce the bug with CVS autoconf, can you please tell us
> how to reproduce it?  It isn't entirely clear from the messages
> already sent to bug-autoconf.  I tried doing this:

>    ./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.

This means the Libtool macros were not found.  You can either
- append the contents of libtool.m4 and ltdl.m4 to aclocal.m4
- append `-I /path/to/$libtool_prefix/share/aclocal' to the arguments
  of aclocal
- just install all autotools below the same $prefix
- edit the file $automake_prefix/share/aclocal/dirlist to contain a line
    /path/to/$libtool_prefix/share/aclocal

Libtool-2.0 and/or Automake-1.10 will allow either one of `libtoolize
--install' or `aclocal --install', and it should do the right thing if
AC_CONFIG_MACRO_DIR was specified in configure.ac and ACLOCAL_AMFLAGS
in toplevel/Makefile.am points aclocal there.

Cheers,
Ralf




reply via email to

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