Yoshiki Hayashi <t90553(a)m.ecc.u-tokyo.ac.jp> writes:
 wmperry(a)aventail.com (William M. Perry) writes:
 
 > Jan Vroonhof <vroonhof(a)math.ethz.ch> writes:
 > 
 > > wmperry(a)aventail.com (William M. Perry) writes:
 > > 
 > > > 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
 > > 
 > > If this could be made into a real patch than this is approved and
 > > retroactively recommended for every XEmacs known to man.
 > 
 > Unfortunately, I don't have the time to hack on it right now... have to get
 > back to real work and housebreaking the new puppy. :)
 
 I made it into real patch. PROBLEMS file is not exactly
 clear about what version is OK and what version is not.
 Does egcs 1.0 means from egcs-1.0 to egcs-1.0.3a?
 
 Also, I don't have access to systems other than Solaris 2.6
 (sparc), Debian GNU/Linux potato (i686) and RedHat Linux 5.2
 (sparc), so I cannot test on other platforms. egcs test is
 not tested yet because I don't have egcs here.
 
 Could someone please test this patch before I send it to
 xemacs-patches? You need to run autoconf after applying this
 patch. Thanks. 
There should probably be some way to turn off these checks, just in case
they get a false positive.  Or a developer _wants_ to compile with known
bad configurations to try and fix the
problem. --i-know-what-im-doing-dammit=yes ?
-bp