Hello, David!
> checking for a BSD compatible install... //1/tmp/autoconf/install-sh -c
> checking whether build environment is sane... yes
> checking whether make sets ${MAKE}... yes
> checking for working aclocal... missing
> checking for working autoconf... missing
> checking for working automake... missing
> checking for working autoheader... missing
> checking for working makeinfo... missing
What a relief! I thought I really had messed up something.
> checking for gm4... no
> checking for gnum4... no
> checking for m4... /usr/local/bin/m4
> checking whether m4 supports frozen files... yes
> checking for mawk... no
> checking for gawk... no
> checking for nawk... no
> checking for awk... awk
> checking for working help2man... missing
> checking for perl... no
> configure: WARNING: autoscan will not be built since perl is not found
> checking for a BSD compatible install... //1/tmp/autoconf/install-sh -c
> creating ./config.status
> creating tests/atconfig
>
> Would you like the config.status as well or should I turn some sort of
> debug logging on?
You still don't show me the problem.
Is config.status run by configure?
Do makefiles exist after that?
What happens if you run "make"?
What happens if you run "make check"?
Regards,
Pavel Roskin
