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 run babel.jar during the bulid.
Am I not supposed to run a gcj-created .jar using kaffe? I could specify an alternative JIT/interpreter... But the gcj-3.2-compiled .jar works quite well with kaffe (at least with the old kaffe, I haven't checked with kaffe-1.1). On Fri, 2003-10-17 at 00:30, Ean Schuessler wrote: > 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 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'. > > > >>retitle 197090 Assertion failure during babel run/build > >> > >Bug#197090: gcj-3.3: babel fails with 3.3, works with 3.2... > >Changed Bug title. > > > >>thanks > >> > >Stopping processing here. -- -Adam P. GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Welcome to the best software in the world today cafe! http://lyre.mit.edu/~powell/The_Best_Stuff_In_The_World_Today_Cafe.ogg
