3.3.2 md5sum - was: Re: sparc-sun-sol2.5.1, g77 config error forgcc-3.3.1

[Hugh Sasse Staff Elec Eng <hgs at dmu dot ac dot uk>]

I was about to send the message below when I found that 3.3.2 is
out. It has enough fixes for sparc and solaris to make the effort of
a rebuild worthwhile.  However, I can't find an md5sum for it on the
web anywhere, and don't have the tools to deal with the sig file
instead. Does anyone know where I should look for the md5sum?

Meanwhile, I suspect I will run into this again so if anyone has
answers to the questions below I'd be grateful.

        Thank you
        Hugh

On Thu, 16 Oct 2003, Toon Moene wrote:

> Well, it's more like: You shouldn't use the default shell, and - given
> that ksh is installed on Solaris - you'll better off using that.
>
Thank you. I have managed to get much further now, having used csh
and updated binutils.  I now have:

Native configuration is sparc-sun-solaris2.5.1

                === libjava tests ===

Schedule of variations:
    unix

Running target unix
Using /usr/local/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/local/share/dejagnu/config/unix.exp as generic interface file for target.
Using /apps/hgs/gcc-3.3.1/libjava/testsuite/config/default.exp as tool-and-target-specific interface file.
Running /apps/hgs/gcc-3.3.1/libjava/testsuite/libjava.compile/compile.exp ...
FAIL: PR1343 compilation from bytecode
FAIL: PR1343 -O compilation from bytecode
FAIL: PR238 compilation from bytecode
FAIL: PR238 -O compilation from bytecode
FAIL: PR295 compilation from bytecode
FAIL: PR295 -O compilation from bytecode
FAIL: SuperConstr compilation from bytecode
FAIL: SuperConstr -O compilation from bytecode
FAIL: XercesBug compilation from bytecode
FAIL: XercesBug -O compilation from bytecode
FAIL: inner_1 compilation from bytecode
FAIL: inner_1 -O compilation from bytecode
FAIL: inner_data compilation from bytecode
FAIL: inner_data -O compilation from bytecode
FAIL: inner_inherit compilation from bytecode
FAIL: inner_inherit -O compilation from bytecode
FAIL: inner_priv compilation from bytecode
FAIL: inner_priv -O compilation from bytecode
FAIL: inner_pub compilation from bytecode
FAIL: inner_pub -O compilation from bytecode
FAIL: not_a_redef compilation from bytecode
FAIL: not_a_redef -O compilation from bytecode
FAIL: pr172 compilation from bytecode
FAIL: pr172 -O compilation from bytecode
FAIL: pr174 compilation from bytecode
FAIL: pr174 -O compilation from bytecode
FAIL: pr176 compilation from bytecode
FAIL: pr176 -O compilation from bytecode
FAIL: static_2 compilation from bytecode
FAIL: static_2 -O compilation from bytecode
FAIL: static_3 compilation from bytecode
FAIL: static_3 -O compilation from bytecode
FAIL: static_inner compilation from bytecode
FAIL: static_inner -O compilation from bytecode
Running /apps/hgs/gcc-3.3.1/libjava/testsuite/libjava.jacks/jacks.exp ...
Running /apps/hgs/gcc-3.3.1/libjava/testsuite/libjava.jni/jni.exp ...
Running /apps/hgs/gcc-3.3.1/libjava/testsuite/libjava.lang/lang.exp ...
FAIL: Array_3 execution - gij test
FAIL: Array_3 execution - gij test
FAIL: FileHandleGcTest execution - source compiled test
FAIL: FileHandleGcTest execution - gij test
FAIL: FileHandleGcTest execution - bytecode->native test
FAIL: FileHandleGcTest -O execution - source compiled test
FAIL: FileHandleGcTest execution - gij test
FAIL: FileHandleGcTest -O execution - bytecode->native test
WARNING: program timed out.
FAIL: SyncTest execution - gij test
WARNING: program timed out.
FAIL: SyncTest execution - bytecode->native test
WARNING: program timed out.
FAIL: SyncTest execution - gij test
WARNING: program timed out.
FAIL: SyncTest -O execution - bytecode->native test
FAIL: Thread_Interrupt output - source compiled test
FAIL: Thread_Interrupt output - gij test
FAIL: Thread_Interrupt output - bytecode->native test
FAIL: Thread_Interrupt -O output - source compiled test
FAIL: Thread_Interrupt output - gij test
FAIL: Thread_Interrupt -O output - bytecode->native test
FAIL: Throw_2 execution - source compiled test
FAIL: Throw_2 execution - gij test
FAIL: Throw_2 execution - bytecode->native test
FAIL: Throw_2 -O execution - source compiled test
FAIL: Throw_2 execution - gij test
FAIL: Throw_2 -O execution - bytecode->native test
Running /apps/hgs/gcc-3.3.1/libjava/testsuite/libjava.loader/loader.exp ...
Running /apps/hgs/gcc-3.3.1/libjava/testsuite/libjava.mauve/mauve.exp ...

                === libjava Summary ===

# of expected passes            2915
# of unexpected failures        58
# of expected failures          16
# of untested testcases         30
gmake[4]: *** [check-DEJAGNU] Error 1
gmake[4]: Leaving directory `/apps/hgs/gcc-build/sparc-sun-solaris2.5.1/libjava/testsuite'
gmake[3]: *** [check-am] Error 2
gmake[3]: Leaving directory `/apps/hgs/gcc-build/sparc-sun-solaris2.5.1/libjava/testsuite'
gmake[2]: *** [check-recursive] Error 1
gmake[2]: Leaving directory `/apps/hgs/gcc-build/sparc-sun-solaris2.5.1/libjava'
gmake[1]: *** [check-target-libjava] Error 2
gmake[1]: Leaving directory `/apps/hgs/gcc-build'
gmake: *** [check] Error 2


So my questions are now:
Do the libjava tests normally report anything positive, or should I
take the total lack of PASS lines here as a seriously bad sign?