Toad ([EMAIL PROTECTED]) wrote:

> Also, Kaffe 1.0.7 will not reliably or full featuredly work with
> Freenet. You will need to bundle or maintain separately a CVS snapshot
> of Kaffe 1.1. Finally, even Kaffe 1.1.x-cvs doesn't work with the new
> nio code in the unstable branch, although sources tell me that may be
> fixed in the not too distant future, and GCJ support is rapidly getting
> there.

I use the stable build of Freenet (currently 598) on an OpenBSD
i386 box using a Kaffe CVS snapshot from May 15.  This was about 3
weeks before the Kaffe 1.1.0 release.  The 1.1.0 version does not
work as well as this older snapshot, for me; it leaks memory much
faster, and FEC splitfile decoding has never worked a single time
for me (though I don't understand why).

However, to get the May 15 version to work, it's necessary to rename
(or remove) the servlet.jar file from Kaffe's jre/lib directory.
(This is not necessary with the 1.1.0 release.)  I don't know
whether there's any way to override this .jar file from the Kaffe
command line.

As mentioned above, Kaffe does not yet support nio, so it won't
run the unstable branch of Freenet, which got nio code added about
a week ago.  The only version of Java that works with nio right now
is the hideously-non-free Sun implementation, version 1.4.1.  Some
people have tried getting gcj to compile a native Freenet package,
with a certain degree of success; but it's not ready for general use.

Kaffe leaks memory, and occasionally crashes, while running Freenet.
For a Debian package, this means it would probably have to be wrapped
in a shell script that reinvokes it in an infinite loop (and a sleep
statement to slow it down, in case it crashes immediately).  This
is, of course, an ugly kludge.

-- 
Greg Wooledge                  |   "Truth belongs to everybody."
[EMAIL PROTECTED]              |    - The Red Hot Chili Peppers
http://wooledge.org/~greg/     |

Attachment: pgp00000.pgp
Description: PGP signature

Reply via email to