From owner-freebsd-java Fri May 24 13:58:36 2002 Delivered-To: freebsd-java@freebsd.org Received: from email.agssmf.com (email.agssmf.com [63.196.107.134]) by hub.freebsd.org (Postfix) with ESMTP id 184B537B406 for ; Fri, 24 May 2002 13:58:32 -0700 (PDT) Received: from newtim (smf68.smf.intranet [172.20.24.68]) by email.agssmf.com (8.11.1/8.11.1) with ESMTP id g4OKwVw88493; Fri, 24 May 2002 13:58:31 -0700 (PDT) (envelope-from tim_schafer@agship.com) From: "Tim E Schafer" To: "'Greg Lewis'" Cc: "'Java FreeBSD'" Subject: RE: All Linux JDK with Hotspot or JIT unstable on FreeBSD Date: Fri, 24 May 2002 13:56:28 -0700 Message-ID: <04ec01c20365$79bb6660$441814ac@newtim> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <20020525020759.A59801@misty.eyesbeyond.com> 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 Thanks, I'll have a look at that I'm probably going to hold out for the native port though. Based on the fact that the native port when released as binary will be certified ... where as the Linux one is already certified, yet there isn't any way to guarantee that FreeBSD Linux compatibility is certifiably as good as native Linux (at least I don't know of such a test) -------------------------------------------- Tim E Schafer tim_schafer@agship.com Programmer 800-562-9915 x190 or 916-376-6190 Associated Global Systems 3231 Evergreen Ave West Sacramento, CA 95691 -------------------------------------------- -----Original Message----- From: owner-freebsd-java@FreeBSD.ORG [mailto:owner-freebsd-java@FreeBSD.ORG] On Behalf Of Greg Lewis Sent: Friday, May 24, 2002 9:38 AM To: Tim E Schafer Cc: 'Java FreeBSD' Subject: Re: All Linux JDK with Hotspot or JIT unstable on FreeBSD On Fri, May 24, 2002 at 09:15:13AM -0700, Tim E Schafer wrote: > While I understand that hotspot and native threads are separate things > I noticed that when I use -classic with the Sun Linux JDK 1.3.1 it > doesn't seem to use native threads either > > So I figured it was an all or nothing thing. Hmm, looks like the Sun .java_wrapper currently enforces that for Linux: if [ "${vmtype}" = "classic" ]; then ttype=green_threads LD_BIND_NOW=yes export LD_BIND_NOW _JVM_THREADS_TYPE=green_threads export _JVM_THREADS_TYPE fi > You could try removing the green_threads setting and see how it goes. I was assuming because FreeBSD doesn't force a threading subsystem that Linux wouldn't, but it looks like I was wrong. BTW, mandating a specific threading subsystem goes against a core tenet of Java. For instance, the JCK testing suite specifically disallows tests that rely on a specific underelying threading model. -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message