Gunnar Evermann <ge204(a)eng.cam.ac.uk> writes:
what exactly is the point pf the second block? Do we really want to
prevent people using -O1 or no optimisation at all from building
XEmacs. If so, we should adjust the message.
It was supposed to do what message said.
Here's the patch.
2000-10-11 Yoshiki Hayashi <yoshiki(a)xemacs.org>
* configure.in: Fix broken gcc detection for 2.7.2.
Index: configure.in
===================================================================
RCS file: /usr/CVSroot/XEmacs/xemacs/configure.in,v
retrieving revision 1.111.2.128
diff -u -r1.111.2.128 configure.in
--- configure.in 2000/10/10 06:53:46 1.111.2.128
+++ configure.in 2000/10/11 07:04:59
@@ -1951,10 +1951,10 @@
AC_MSG_ERROR(Aborting due to known problem)
;;
*:i*86*:2.7.2*)
- case "$GCC_VERSION" in
- 2.7.2)
- case "$CFLAGS" in
- *-O2*|*-O3*)
+ case "$CFLAGS" in
+ *-O2*|*-O3*)
+ case "$GCC_VERSION" in
+ 2.7.2)
case "$CFLAGS" in
*-fno-strength-reduce*) ;;
*)
@@ -1966,17 +1966,17 @@
esac
;;
esac
+ case "$CFLAGS" in
+ *-fno-caller-saves*) ;;
+ *)
+ AC_MSG_RESULT(yes)
+ AC_MSG_WARN(Don't use -O2 with gcc 2.7.2 under Intel/XXX without also using)
+ AC_MSG_WARN(-fno-caller-saves.)
+ AC_MSG_ERROR(Aborting due to known problem)
+ ;;
+ esac
;;
esac
- case "$CFLAGS" in
- *-fno-caller-saves*) ;;
- *)
- AC_MSG_RESULT(yes)
- AC_MSG_WARN(Don't use -O2 with gcc 2.7.2 under Intel/XXX without also using)
- AC_MSG_WARN(-fno-caller-saves.)
- AC_MSG_ERROR(Aborting due to known problem)
- ;;
- esac
;;
esac
AC_MSG_RESULT(no)
--
Yoshiki Hayashi