This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

PATCH: GCC 3.2 suddenly fails every java test, CLASSPATH wrong


On Thu, Aug 15, 2002 at 08:52:45PM +0200, Mark Wielaard wrote:
> Hi,
> 
> On Thu, 2002-08-15 at 17:05, H. J. Lu wrote:
> > On Thu, Aug 15, 2002 at 11:01:29AM -0400, Kaveh R. Ghazi wrote:
> > > All of a sudden, every test in the java testsuite is failing in GCC-3.2:
> > > http://gcc.gnu.org/ml/gcc-testresults/2002-08/msg00486.html
> > > 
> > > It's not just me:
> > > http://gcc.gnu.org/ml/gcc-testresults/2002-08/msg00462.html
> > > 
> > > In the logfile, all of the failures look like this:
> > > 
> > >  > Can't find default package `java.lang'. Check the CLASSPATH
> > >  > 	environment variable and the access to the archives
> > >  > 1 error
> > > 
> > > [...]
> > I was wondering the same thing. This works
> > 
> > http://gcc.gnu.org/ml/gcc-testresults/2002-08/msg00457.html
> > 
> > because I have gcc 3.2 installed on that machine. All my other machines
> > failed. I thought it might be my new binutils :-). It has to be fixed.
> 
> I just tested the official gcc-3.2.tar.gz release from ftp.gnu.org and
> it works for me.
> 
> === libjava Summary ===
> 
> # of expected passes		2075
> # of expected failures		18
> # of untested testcases		14
> 
> See: http://gcc.gnu.org/ml/gcc-testresults/2002-08/msg00489.html
> 
> This was on a i686-pc-linux-gnu machine running:
> 
> Debian GNU/Linux testing/unstable
> Linux 2.4.18
> binutils Version: 2.12.90.0.15-1
> glibc Version: 2.2.5-13
> 
> With the following configure flags:
> --enable-clocale=gnu --enable-shared --enable-threads=posix
> --enable-languages=c++,java --prefix=/usr/local/gcc32
> 
> I know that at least for the CVS HEAD (3.3) you will need the above
> binutils on powerpc-unknown-linux-gnu and maybe other architectures.
> 
> 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.

"make install" shouldn't be required. It is a bug. This one works for
me.


H.J.

Attachment: gcc-testsuite-libjava.patch
Description: Text document


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]