> If its a bug in autoconf itself, we can patch the autoconf .m4
> files directly on Hub.Org, and just make sure we autoconf with that...I
> have no problemsm with that...
*** acspecific.m4.orig Thu Oct 29 12:43:02 1998
--- acspecific.m4 Thu Oct 29 12:49:39 1998
***************
*** 81,87 **** AC_PROG_CC_WORKS AC_PROG_CC_GNU
! if test $ac_cv_prog_gcc = yes; then GCC=yes dnl Check whether -g works, even if CFLAGS is set, in case the package
dnlplays around with CFLAGS (such as to build both debugging and
--- 81,87 ---- AC_PROG_CC_WORKS AC_PROG_CC_GNU
! if test "$ac_cv_prog_gcc" = yes; then GCC=yes dnl Check whether -g works, even if CFLAGS is set, in case the
packagednl plays around with CFLAGS (such as to build both debugging and
***************
*** 215,221 **** AC_DEFUN(AC_PROG_GCC_TRADITIONAL, [AC_REQUIRE([AC_PROG_CC])dnl AC_REQUIRE([AC_PROG_CPP])dnl
! if test $ac_cv_prog_gcc = yes; then AC_CACHE_CHECK(whether ${CC-cc} needs -traditional,
ac_cv_prog_gcc_traditional,[ ac_pattern="Autoconf.*'x'"
--- 215,221 ---- AC_DEFUN(AC_PROG_GCC_TRADITIONAL, [AC_REQUIRE([AC_PROG_CC])dnl AC_REQUIRE([AC_PROG_CPP])dnl
! if test "$ac_cv_prog_gcc" = yes; then AC_CACHE_CHECK(whether ${CC-cc} needs -traditional,
ac_cv_prog_gcc_traditional,[ ac_pattern="Autoconf.*'x'"
Should work... if the other message is correct about the source of the
problem. There really needs to be a sanity check for --with-cc or whatever
it is.
Taral
