If we don't seem to have an ANSI compiler, then omit a warning as soon
as that is discovered, because it is likely to break later configure
tests. This doesn't seem to catch the particular HP-UX compiler I was
after, which is non-ANSI but only emits a warning on this configure
test. Nevertheless probably better to have it in.
FreeBSD 3.3-RELEASE i386 cc
FreeBSD 4.1.1-RELEASE i386 cc
FreeBSD 4.3-STABLE i386 cc
- HP-UX 10.10 gcc
- HP-UX 11.11 cc
+ HP PA-RISC HP-UX 10.20 gcc
+ HP PA-RISC HP-UX 11.11 cc
IRIX 6.5 MIPS cc
IRIX 6.5 MIPS gcc
Mac OS X PPC (--disable-ipv6) cc
AC_CONFIG_HEADER(config.h)
AC_PREREQ(2.52)
+RSYNC_VERSION=2.4.7pre5
+AC_SUBST(RSYNC_VERSION)
+AC_MSG_NOTICE([Configuring rsync $RSYNC_VERSION])
+
+AC_DEFINE_UNQUOTED(RSYNC_VERSION, ["$RSYNC_VERSION"], [rsync release version])
+
LDFLAGS=${LDFLAGS-""}
AC_CANONICAL_TARGET([])
AC_PROG_CC
AC_PROG_CPP
AC_PROG_INSTALL
+AC_PROG_CC_STDC
AC_SUBST(SHELL)
-RSYNC_VERSION=2.4.7pre4
-AC_SUBST(RSYNC_VERSION)
-AC_DEFINE_UNQUOTED(RSYNC_VERSION, ["$RSYNC_VERSION"], [rsync release version])
+if test "$xac_cv_prog_cc_stdc" = xno
+then
+ AC_MSG_WARN([rsync requires an ANSI C compiler and you don't seem to have one])
+fi
# compile with optimisation and without debugging by default, unless
# --debug is given. We must decide this before testing the compiler.