Hello again,
The newest gcj-3.3 now compiles babel just fine (as mentioned when
closing Debian bug 209283). A new bug in kaffe's jar prevents the
archive from building. But when fastjar (from gcj) is used instead of
kaffe jar, it builds just fine, and kaffe's JVM runs it just fine; the
babel tes
Yup, that's the problem.
Babel is an SIDL compiler; SIDL is an IDL like CORBA. Babel is
implemented in Java, and needs to run in order to generate the stub
files for its runtime front ends in C, C++, F77, and python (equivalent
to, say, liborbit.a, etc.). So the babel shell script uses kaffe to
With gjc-3.3 it compiles but fails at runtime with Kaffe?!?
I take it that you are compiling a class file with gcj and trying to run
it with Kaffe?
Debian Bug Tracking System wrote:
Processing commands for [EMAIL PROTECTED]:
reopen 197090
Bug#197090: gcj-3.3: babel fails with 3.3, works w
Processing commands for [EMAIL PROTECTED]:
> reopen 197090
Bug#197090: gcj-3.3: babel fails with 3.3, works with 3.2...
Bug reopened, originator not changed.
> reassign 197090 kaffe
Bug#197090: gcj-3.3: babel fails with 3.3, works with 3.2...
Bug reassigned from package `gcj-3.3' to `kaffe'.
> r
4 matches
Mail list logo
