This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: java/6092: sparc-sun-solaris2.7 has hundreds of libjava failures with -m64
- From: Tom Tromey <tromey at redhat dot com>
- To: nobody at gcc dot gnu dot org
- Cc: gcc-prs at gcc dot gnu dot org,
- Date: 31 Mar 2002 05:46:03 -0000
- Subject: Re: java/6092: sparc-sun-solaris2.7 has hundreds of libjava failures with -m64
- Reply-to: Tom Tromey <tromey at redhat dot com>
The following reply was made to PR java/6092; it has been noted by GNATS.
From: Tom Tromey <tromey@redhat.com>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: java/6092: sparc-sun-solaris2.7 has hundreds of libjava failures with -m64
Date: 30 Mar 2002 22:42:47 -0700
>>>>> "Kaveh" == Kaveh R Ghazi <ghazi@caip.rutgers.edu> writes:
Kaveh> Alternatively, you could get a solaris2 box and run make check
Kaveh> with: setenv RUNTESTFLAGS "--verbose
Kaveh> --target_board='unix{-m64,}'" to get both regular and -m64
Kaveh> passes.
I assume I need a special 64 bit machine to do this.
I don't know whether I have access to one.
Kaveh> No I think it's really a bug. If you look back, I specifically
Kaveh> showed the `ldd' results to prove I was using the correct
Kaveh> shared libs for 64-bit compilation. (The sparcv9 multilibs
Kaveh> *are* built with -m64.)
Ok, thanks. I didn't know dejagnu knew about multilibs.
As far as I know nobody has ever tried libgcj on a 64-bit Sparc box
before. It sounds like this requires actual debugging; I was hoping
it was some relatively simple thing.
Tom