Dalibor just removed kjc.jar from our CVS. We were already discussing ways of redoing the build and packaging, and the bootstrapping process with kjc.jar has been painful, to say the least. So we were going to redesign the packaging process altogether anyhow.
Yeah, it is pretty hard to bootstrap correctly on ports where kaffe's jit/intepreter is not up to running large beasts like kjc on GNU Classpath :) That's a pretty good test of the VM.
I think I want to propose separating the whole JDK part (eg. javac and relating utils) out from Kaffe, and make the main product of Kaffe be just the JRE. Ideally, we could split off the class libraries as well, since that comes from Classpath mostly now. So the build process could be something like:>
a) download Kaffe, KJC, and Classpath separately b) Run some build script which builds a JDK
That's less nice than our current solution of having one tarball that gets downloaded. But I really think Kaffe should just be the virtual machine itself, not an entire distribution.
Absolutely. We're some 29 classes away from being fully synced up with GNU Classpath, so it's pretty close now. I think we'll get there for the next release.
In the meantime, can't the Debian package just be modified to include the kjc source tarball and related patches? They are available. That should fix the bug.
Sure. I'll fix the remaining problems Arnaud reported to me, make jikes build the default one, then he can upload a new kaffe package without kjc, and repackage kjc straight from Kaffe's CVS module. That should fix it all.
cheers, dalibor topic
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
