[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
AC_PROG_CC now required?
|
From: |
Harlan Stenn |
|
Subject: |
AC_PROG_CC now required? |
|
Date: |
Tue, 24 Apr 2001 01:33:56 -0400 |
|
User-agent: |
EMH/1.10.0 SEMI/1.13.3 (Komaiko) FLIM/1.12.7 (Y.Dþzaki) XEmacs/21.1 (patch 12) (Channel Islands) (i386--freebsd) |
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:
address@hidden> 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
address@hidden>
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
- AC_PROG_CC now required?,
Harlan Stenn <=