The initializeSystemClass method being present is just a good indicator
of a version of the classes.zip file that we cannot run with.
The problem with sun's shoddy release practices is that this method
seems to pop up in newer releases of the JDK from sun (and it's various
licensees). There really is *no* reason for this method -- it should be
handled in the static initializer. sorta strange that the method exists
at all.
There are two sources of the jdk that are know to work:
- JDK 1.1.5v7 for Linux glibc from Blackdown
-
ftp://ftp.freebsd.org/pub/FreeBSD/packages/All/jdk1.1.6.V98-8-14.tar.gz
are you sure you grabbed the 1.1.5v7 linux version?
> My question is how does japhar handle setting of the System.in, System.out,
> and System.err if it is not going to do it the same way as the sun JDK?
we do do it the same way as the JDK. it's just that different revisions
of the JDK (and different releases of the same revision - whee, isn't
java WONDERFUL!?) do it differently. and, since sun's license doesn't
let us release the classes.zip file along with japhar, we have this
mess.
don'tcha just love sun?
xtoph
