After a long 6 hour compile that ended in a failure on a plugin
target, I had a fresh native 1.4.1 image (with HotSpot no less!)
for my 4.7-stable box. I've been running a couple of tomcat apps
pretty heavily for the past few hours, and things seem stable, aside
from a few DEBUG: signal messages. Aside from apparent stability,
the performance improvement over native 1.3.1 is about 600%.
Now, a nit... I tried building on a -current machine, but the
3.2.1 compiler bails early in the build of adlc, complaining of
numerous ostream operator link-errors. I hacked around with
this a bit, while the 4.7 box was building, but gave up after
I noticed that I could compile the same ostream<<(char) code
that the build was complaining about. Weird.
In any case, kudos Alexey, for the fine work. If there is any
legwork that I could do in getting 3.2.1 compiling on -current,
let me know; I'd be glad to help.
I created a ports directory for the jdk14, and was wondering if
it would be possible to distribute patchset 2 in .zip format, so
USE_ZIP could be set in the Makefile to extract both the scsl-src
and patchset, instead of having to _manually_ extract one of them.
If I'm missing some feature of the ports system that would allow
automatic extraction of both, please throw that cluestick at me :-)
On the HotSpot note, is there any work being done on getting 1.3.1's
HotSpot working? AFAIR, it would not build with 1.3.1-patchset-7.
 one of these is signal 11, so if this is _the_ signal 11?I'm
familiar with, and you want to know how to duplicate, I could
probably distill a testcase.
"Develop your talent, man, and leave the world something. Records are
really gifts from people. To think that an artist would love you enough
to share his music with anyone is a beautiful thing." -- Duane Allman
with "unsubscribe freebsd-java" in the body of the message