On 11/04/2005, at 11:23 PM, Ranjit Mathew wrote:

Geoffrey Keating wrote:
[...]
which I see you've already committed a patch for, and a large number
of Java failures.

You can see full test results at
[...]

<http://gcc.gnu.org/ml/gcc-testresults/2005-04/msg00814.html>

for 4.0.0-20050410.

It might be helpful to put your "libjava.log" somewhere or if all the Java failures seem similar, to post the error messages around the "FAIL" lines from your libjava.log.

Many seem to be NoClassDefFoundError exceptions. Some examples of those plus all the unusual cases are:

Setting LD_LIBRARY_PATH to .:/Volumes/Unused/geoffk/gcc-4.0.0-20050410/powerpc-apple-darwin8.0.0/ ./libjava/.libs:/Volumes/Unused/geoffk/gcc-4.0.0-20050410/gcc:.:/ Volumes/Unused/geoffk/gcc-4.0.0-20050410/powerpc-apple-darwin8.0.0/./ libjava/.libs:/Volumes/Unused/geoffk/gcc-4.0.0-20050410/gcc:.:/Volumes/ Unused/geoffk/gcc-4.0.0-20050410/powerpc-apple-darwin8.0.0/./libjava/ .libs:/Volumes/Unused/geoffk/gcc-4.0.0-20050410/gcc
Exception in thread "main" java.lang.RuntimeException: test failed:5
<<No stacktrace available>>
FAIL: Array_3 -O3 execution - bytecode->native test
UNTESTED: Array_3 -O3 output - bytecode->native test
...
Testing class `Class_1'...
Exception in thread "main" java.lang.NoClassDefFoundError: C
<<No stacktrace available>>
FAIL: Class_1 execution - gij test
...
Exception in thread "Thread-1" Exception in thread "Thread-2" Exception in thread "Thread-3" Exception in thread "Thread-4" java.lang.NoClassDefFoundError: SyncTest
<<No stacktrace available>>
java.lang.NoClassDefFoundError: SyncTest
<<No stacktrace available>>
java.lang.NoClassDefFoundError: SyncTest
<<No stacktrace available>>
java.lang.NoClassDefFoundError: SyncTest
<<No stacktrace available>>
fail: 0
FAIL: SyncTest execution - gij test
UNTESTED: SyncTest output - gij test
...
PASS: stringconst2 execution - gij test
FAIL: stringconst2 output - gij test

I can mail the full log to anyone interested, but I don't think the list needs it.

Attachment: smime.p7s
Description: S/MIME cryptographic signature



Reply via email to