Latest CVS autoconf.
I have several autoconf packages that do not do any compiling, so I don't
bother to call AC_PROG_CC .
However, the generated "configure" script seems to want to find the C
preprocessor, and this fails with:
harlan@puss> configure
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for mawk... no
checking for gawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets ${MAKE}... yes
checking whether make sets ${MAKE}... (cached) yes
checking build system type... i386-unknown-freebsdelf4.3
checking how to run the C preprocessor... /lib/cpp
configure: error: C preprocessor "/lib/cpp" fails sanity check
harlan@puss>
While I can easily hack around this by adding an AC_PROG_CC to my
configure.in, I was thinking this may be a bug...
H
