[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: |
Paul Eggert |
Subject: |
Re: echo "enhancement" leads to confused legacy script tools... |
Date: |
Sun, 19 Mar 2006 18:04:43 -0800 |
User-agent: |
Gnus/5.1007 (Gnus v5.10.7) Emacs/21.4 (gnu/linux) |
Linda W <address@hidden> writes:
> I already have 2.59 installed on my system, "2.59-80.1" from
> SuSE9.3. So it was with 2.59 autoconf that I originally ran into the
> problem.
OK. Can you reproduce it with CVS autoconf? Here's how to build it:
cvs -z3 -d:pserver:address@hidden:/sources/autoconf co autoconf
cd autoconf
./configure --prefix=$HOME/prefix # substitute your favorite directory here
make
make install
$HOME/prefix/bin/autoconf --version
and then prepend $HOME/prefix/bin (or whatever) to your $PATH.
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:
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
autoconf failed
Autotool bootstrapping failed. You will need to investigate and correct
before you can develop on this source tree
I am using Autoconf 2.59 (Debian stable), Libtool 1.5.22, and Automake
1.9.6.
Thanks.
- Re: echo "enhancement" leads to confused legacy script tools..., Linda W, 2006/03/19
- Re: echo "enhancement" leads to confused legacy script tools..., Paul Eggert, 2006/03/19
- Re: echo "enhancement" leads to confused legacy script tools..., Henrik Nordstrom, 2006/03/20
- Re: echo "enhancement" leads to confused legacy script tools..., Paul Eggert, 2006/03/19
- Re: echo "enhancement" leads to confused legacy script tools..., Linda W, 2006/03/20
- Re: echo "enhancement" leads to confused legacy script tools...,
Paul Eggert <=
- Re: echo "enhancement" leads to confused legacy script tools..., Ralf Wildenhues, 2006/03/20
- Re: echo "enhancement" leads to confused legacy script tools..., Henrik Nordstrom, 2006/03/20
- Re: echo "enhancement" leads to confused legacy script tools..., Paul Eggert, 2006/03/20
- Re: echo "enhancement" leads to confused legacy script tools..., Henrik Nordstrom, 2006/03/20
- Re: echo "enhancement" leads to confused legacy script tools..., Linda W, 2006/03/20
- Re: echo "enhancement" leads to confused legacy script tools..., Ralf Wildenhues, 2006/03/21
- Re: echo "enhancement" leads to confused legacy script tools..., Ralf Wildenhues, 2006/03/21
- Re: echo "enhancement" leads to confused legacy script tools..., Ralf Wildenhues, 2006/03/21
- Re: echo "enhancement" leads to confused legacy script tools..., Henrik Nordstrom, 2006/03/21
- bad m4 quotation? (was: echo "enhancement" leads to confused legacy script tools...), Ralf Wildenhues, 2006/03/27