On Wed, Jan 17, 2001 at 06:09:34PM +0000, Lars Hecking wrote:
> Akim Demaille writes:
> > Will be applied within a couple of minutes.
>
> I don't think this is working as intended.
>
> cvs automake as of now. autoconf 2.13.
>
> $ ./configure
> creating cache ./config.cache
> checking for a BSD compatible install... /usr/local/gnu/bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... gawk
> checking whether make sets ${MAKE}... yes
> checking for perl... /bin/perl
> updating cache ./config.cache
> creating ./config.status
> creating Makefile
> creating automake
> creating aclocal
> creating m4/Makefile
> creating tests/Makefile
> $ make dist
> cd . && /tmp/automake/aclocal --acdir=m4
> cd . && /tmp/automake/automake --amdir=. --gnits Makefile
> cd . && /bin/sh /tmp/automake/missing --run autoconf
> /bin/sh ./config.status --recheck
> running /bin/sh ./configure --no-create --no-recursion
> loading cache ./config.cache
> checking for a BSD compatible install... (cached) /usr/local/gnu/bin/install -c
> checking whether build environment is sane... yes
> checking for mawk... (cached) gawk
> checking whether make sets ${MAKE}... (cached) yes
> checking for perl... (cached) /bin/perl
> creating ./config.status
> cd . \
> && CONFIG_FILES=Makefile CONFIG_HEADERS= /bin/sh ./config.status
> creating Makefile
> make: *** No rule to make target `@CONFIGURE_AC@', needed by `stamp-vti'. Stop.
> $
Did you install completely automake? I don't see that problem showing
up. Could you deonstrate the failure in a few steps? Did the test suite
run OK?
