[kaffe] Warning: Unrecognized version number 47/0 in classfile.

Gerlando Falauto iurly at writeme.com
Mon Jun 30 04:14:01 PDT 2003

Ciao Dalibor!

> Please note that jikes 1.14 and 1.15 have bugs that result in a
> miscompiled Klasses.jar file.

Yep, I wasted the entire afternoon yesterday before I figured that out.
Wish you had told me earlier... Sgrunt! ;-)

> If you use jikes 1.18, you need to pass it the "-source 1.1" option.

I used -target 1.1 but that didn't seem to help... or was it just that it
wasn't rebuilding all files? Whatever, I'll keep that in mind.

> > And how (using which tool) was the distribution 1.0.7 Klasses.jar built
> > to begin with?
> I don't know anymore. You can try to figure it out by building it with jikes
> 1.13, 1.15, 1.16 and 1.17, as well as with kjc and compare the resulting files.

My ported kaffe is very very unstable so I am afraid to touch
Klasses.jar again. Plus, I get very weird behaviors when I try to feed
it some Klasses from an uncompressed directory (even if they are just
uncompressed from the original Klasses.jar!). Do you have any idea what
evil classloading mechanism could be the cause of that? I am desperately
trying to speed up the VM startup but that only makes things worse...

Just to make sure I'm not making false assumptions:  does kaffeh have
anything to do with how classes (and kaffe itself)  are compiled or
loaded? I mean I assumed kaffeh would have been totally
platform-independent, so I am using the kaffeh binary that was built when
I compiled kaffe-1.0.7/i386-linux. Was that a BAD thing?

> A patch that would write the compiler used and its options to the MANIFEST.MF
> file would be cool. Could you create one?

I don't really know a thing about the MANIFEST.MF file and I am not very
comfortable with Makefile.am(s) either. I can give it a try, though, in
the next few days.


More information about the kaffe mailing list