Hi,
With autoconf-2.13, I have been using constructs like the one below
to detect whether gcc is used:
[Similar constructs are used in libiberty, libgloss, newlib and
Cygwin's winsup]
if test $ac_cv_prog_gcc = yes; then
# do something
fi
This test relies on the value of ac_cv_prog_gcc. With CVS
Hi all,
By accident, I just typed in this (autoconf/CVS):
# autoconf --add-missing
autoconf: option `--add-missing' requires an argument
This urged me to play with autoconf's options:
# autoconf --add=missing
/usr/bin/m4: Cannot open missing/autoconf.m4f: No such file or
directory
# autoconf
With CVS-autoconf as of a today:
# cat configure.in
AC_INIT([foo.c])
AC_PROG_CC
AC_PROG_CPP
AC_TRY_LINK([extern void bar() ;], [bar();])
AC_OUTPUT([Makefile])
# autoconf
configure.in:6: warning: AC_PROG_CPP was called before AC_PROG_CC
Where?
Ralf
