From owner-freebsd-java@FreeBSD.ORG Tue Jun 3 10:53:51 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 8E02E37B404; Tue, 3 Jun 2003 10:53:51 -0700 (PDT) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 881C843F85; Tue, 3 Jun 2003 10:53:49 -0700 (PDT) (envelope-from julian@elischer.org) Received: from interjet.elischer.org (12-232-168-4.client.attbi.com[12.232.168.4]) by attbi.com (sccrmhc02) with ESMTP id <2003060317534700200aei15e>; Tue, 3 Jun 2003 17:53:48 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id KAA93298; Tue, 3 Jun 2003 10:53:46 -0700 (PDT) Date: Tue, 3 Jun 2003 10:53:44 -0700 (PDT) From: Julian Elischer To: Daniel Eischen In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-threads@freebsd.org cc: freebsd-java@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 17:53:52 -0000 On Tue, 3 Jun 2003, Daniel Eischen wrote: > On Mon, 2 Jun 2003, Tom Samplonius wrote: > > > > > 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. > > I believe mysql relies on SIGHUP or a fork to handle signals. Mysql > may actually work now, but I haven't tried it. I don't think the JDK > relies on signals other than synchronous signals which should work > OK with libkse. > > I was more interested in the statement that "jdk is only guaranteed > to work with libc_r" that one of the Java developers posted. I > took it to mean that the implementation of our jdk is geared > towards libc_r (perhaps knowing internal stuff about how libc_r > works). I don't want anything like that to stop us, and we > can add some common APIs to the threads libraries if needed > to support it. > > > 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? > > That should be good. A panic fix was checked in yesterday that should be included, so today's is a better bet.. > > -- > Dan Eischen > > _______________________________________________ > freebsd-threads@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-threads > To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org" >