GCC 3.2 suddenly fails every java test, CLASSPATH wrong

[Kaveh R. Ghazi]

 > From: Mark Wielaard <mark@klomp.org>
 > 
 > One thing that I always do before running 'make check -k' is a 'make
 > install' because in the past the tests sometimes picked up the wrong
 > libgcj.jar to test against. Maybe that is still needed. If you haven't
 > done a 'make install' yet could you do that and then run make check in
 > the libjava subdir? Otherwise try updating your binutils to
 > 2.12.90.0.15 or higher and rebuild everything with that.
 > Thanks,
 > Mark

I thought I clearly indicated in my initial report that having a prior
(or current) version of the jar file installed probably made the
warning go away.  That's an explanation why the problem only occurs
for some people and not other, its not the solution.

I agree with HJ, this needs to be fixed.  It's a perception of quality
issue, people will erroneously think gcj is broken when it's in fact a
bug in the testsuite and they'll file spurious bug reports which waste
our time.

		--Kaveh
--
Kaveh R. Ghazi			Director of Systems Architecture
ghazi@caip.rutgers.edu		Qwest Solutions