It's working for me. Install the Sharp compatibility library. Make a shell script for your Java application. Run makecompat on the shell script. Then invoke the shell script. All makecompat does is to put a the path to the Sharp library in your LD_LIBRARY_PATH and create a symbolic link to some file that evm, the Java interpreter, needs before it invokes your original script. You can make a shell script that includes all that and skip running makecompat.
Not the question I asked. What I asked was, has anyone got Jeode running on 3.5.3 in a state that's usable, i.e. have the Compatability issues been fixed and is there anything special I need to do in addition to the usual steps for OZ 3.5.2.
I had Opera running before I stopped using OZ 3.5.3, but it was not stable. Jeode did work for a very short amount of time, but kept needing to be fixed and was not very usable.
There's a thread or two about this around somewhere. "Search" is your friend.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=82851\"][{POST_SNAPBACK}][/a][/div]
I know, I posted to a number of them...
-MF.