From owner-freebsd-java@FreeBSD.ORG Mon Jun 2 22:02:16 2003 Return-Path: Delivered-To: freebsd-java@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8BD5D37B401; Mon, 2 Jun 2003 22:02:16 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [207.200.153.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B51743F93; Mon, 2 Jun 2003 22:02:14 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 19N2KL-0000m9-00; Mon, 2 Jun 2003 20:19:09 -0700 Date: Mon, 2 Jun 2003 20:19:08 -0700 (PDT) From: Tom Samplonius To: Daniel Eischen In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-java@freebsd.org cc: freebsd-threads@freebsd.org Subject: Re: Fwd: Re: Native JDK with libthr/libkse X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jun 2003 05:02:17 -0000 On Mon, 2 Jun 2003, Daniel Eischen wrote: > On Mon, 2 Jun 2003, Tom Samplonius wrote: > > ... > > > And I encourage the java developers to let us threads guys know > > > what they're having problems with. It has been stated that > > > jdk is not guaranteed to work with anything but libc_r, so > > > contact us over at threads@. We want to see a fast and stable > > > jdk as much as anyone else does. > > > > > > -- > > > Dan Eischen > > > > > > But the last that I've seen on the threads@ list is that libkse's signal > > handling is not finished, and both libthr and libkse have incomplete SMP > > support. I've been waiting to hear whether one of these has reached a > > "finished" state, in order that a test build of jdk on FreeBSD 5 is not a > > total waste... > > SMP libkse support should be complete. We are working on signal > handling now, but it's fudged to mostly work. Mozilla, KDE, > and openoffice all run with libkse. Does "fudged" mean that the issue MySQL not exiting has also been resolved? That seems like something that would break a java application real fast. Also at what point was support completed? I'm not sure if I need to cvsup again. I last cvsupped -current on May 31st. Would that be the latest and greatest libkse? > -- > Dan Eischen Tom