From owner-freebsd-java@FreeBSD.ORG Mon Nov 22 19:52:07 2004 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 5BA6116A4CE for ; Mon, 22 Nov 2004 19:52:07 +0000 (GMT) Received: from misty.eyesbeyond.com (glewis.dsl.xmission.com [166.70.56.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id BDE8443D4C for ; Mon, 22 Nov 2004 19:52:06 +0000 (GMT) (envelope-from glewis@eyesbeyond.com) Received: from misty.eyesbeyond.com (localhost.eyesbeyond.com [127.0.0.1]) iAMJq2Bx058394; Mon, 22 Nov 2004 12:52:03 -0700 (MST) (envelope-from glewis@eyesbeyond.com) Received: (from glewis@localhost) by misty.eyesbeyond.com (8.12.11/8.12.11/Submit) id iAMJq1km058393; Mon, 22 Nov 2004 12:52:01 -0700 (MST) (envelope-from glewis@eyesbeyond.com) X-Authentication-Warning: misty.eyesbeyond.com: glewis set sender to glewis@eyesbeyond.com using -f Date: Mon, 22 Nov 2004 12:52:01 -0700 From: Greg Lewis To: Jonathan Belson Message-ID: <20041122195201.GA58381@misty.eyesbeyond.com> References: <52188.192.168.0.3.1101113999.squirrel@192.168.0.3> <2037.192.168.0.1.1101152715.squirrel@192.168.0.1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2037.192.168.0.1.1101152715.squirrel@192.168.0.1> User-Agent: Mutt/1.4.2.1i cc: freebsd-java@freebsd.org Subject: Re: JDK 1.4 build problem under 5.3 release - solution 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: Mon, 22 Nov 2004 19:52:07 -0000 On Mon, Nov 22, 2004 at 07:45:15PM -0000, Jonathan Belson wrote: > I just spent some time comparing configuration options between a stock > 5.3 GENERIC kernel (which runs linux-sun-jdk just fine) and my local > kernel config file. > > After a few iterations, I found the one option which makes or breaks the > port: _KPOSIX_PRIORITY_SCHEDULING. Without it, the VM locks up solidly; > with it, it works fine. > > Does this fix the problem for anyone else? It could certainly be worth > adding a note in UPDATING and/or pkg-message in that case. That rings a bell... I'm sure someone hit something like that with 4.x. Sorry I didn't think of it sooner :(. -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : glewis@FreeBSD.org