Robert Pluim <rpluim(a)bigfoot.com&gt; writes: For some of the problems in PROBLEMS, I would vote for configure hacking to make sure people don't even try to build XEmacs that way unless they know what they are doing. GCC_VERSION=`some magic here` dnl Search for GCC specific build problems we know about if test "$GCC" = "yes"; then case `uname -s`:`uname -m`:$GCC_VERSION in *:sun4*:gcc_281|sun4*egcs_10*) dnl Don't use -O2 with gcc 2.8.1 and egcs 1.0 under SPARC architectures dnl without also using `-fno-schedule-insns'. case "$CFLAGS" in *-O2*) case "$CFLAGS" in *-fno-schedule-insns*) ;; *) AC_MSG_WARN(Don't use -O2 with gcc 2.8.1 and egcs 1.0 under SPARC architectures) AC_MSG_WARN(without also using `-fno-schedule-insns'.) AC_MSG_ERROR(Aborting due to known problem) ;; esac ;; esac ;; Linux:alpha:egcs_11*) AC_MSG_WARN(There have been reports of egcs-1.1 not compiling XEmacs correctly on) AC_MSG_WARN(Alpha Linux. There have also been reports that egcs-1.0.3a is O.K.) AC_MSG_ERROR(Aborting due to known problem) ;; *:i*86*:gcc_272) case "$CFLAGS" in *-O2*) case "$CFLAGS" in *-fno-strength-reduce*) ;; *) AC_MSG_WARN(Don't use -O2 with gcc 2.7.2 under Intel/XXX without also using) AC_MSG_WARN(`-fno-strength-reduce'.) AC_MSG_ERROR(Aborting due to known problem) ;; esac ;; case "$CFLAGS" in *-fno-caller-saves*) ;; *) 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 ;; . . . esac fi -bp