From owner-freebsd-java Mon Jun 24 23: 0:26 2002 Delivered-To: freebsd-java@freebsd.org Received: from gnuppy.monkey.org (wsip68-15-8-100.sd.sd.cox.net [68.15.8.100]) by hub.freebsd.org (Postfix) with ESMTP id 6605437B40D for ; Mon, 24 Jun 2002 23:00:13 -0700 (PDT) Received: from billh by gnuppy.monkey.org with local (Exim 3.35 #1 (Debian)) id 17MjN4-0000Yz-00; Mon, 24 Jun 2002 23:00:10 -0700 Date: Mon, 24 Jun 2002 23:00:10 -0700 To: Marc van Kempen Cc: java@freebsd.org, Bill Huey Subject: Re: Native hotspot JVM Message-ID: <20020625060010.GA2154@gnuppy.monkey.org> References: <3D180579.3040706@bowtie.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D180579.3040706@bowtie.nl> User-Agent: Mutt/1.4i From: Bill Huey Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Jun 25, 2002 at 07:54:01AM +0200, Marc van Kempen wrote: > Eagerly anticipated! > > > I've moved to -current for all of my development now since their libc_r > > system has bug fixes that I don't want to back port to -stable. > > I almost missed this, does this mean it's not possible to make it run on > -stable, or just that you don't want to port the fixes right now and > that you'll leave that to a volunteer? It only works on -stable at this time, but with KSEs coming around the corner and all bug fixes to thread suspension committed to -current, it doesn't really make sense for me to keep developing under -stable. And right, I'd like to get a volunteer to port -current's libc_r to -stable. I tried hacking it myself, but decided that it was a waste of my time and that I should focus on core -current libc_r issues and getting HotSpot working with it instead. BTW, for a pre-alpha release, it runs surprisingly stable. bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message