From owner-freebsd-java Tue Mar 16 21:27:45 1999 Delivered-To: freebsd-java@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 87A7115015 for ; Tue, 16 Mar 1999 21:27:17 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with SMTP id XAA22904; Tue, 16 Mar 1999 23:26:57 -0600 (CST) Date: Tue, 16 Mar 1999 23:26:57 -0600 (CST) From: Steve Price To: Anthony Kimball Cc: freebsd-java@FreeBSD.ORG Subject: Re: the prelease jdk1.2 for linux: problem In-Reply-To: <14063.14629.811288.172253@avalon.east> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 16 Mar 1999, Anthony Kimball wrote: # Quoth Steve Price on Tue, 16 March: # : # : No. '-Djava.comiler=tya' is a valid use if you have the TYA JIT. # : A JIT is usually a .so file and is usually located in a directory # : like '/usr/local/jdk1.2/lib/i386/green_threads/'. # # I had read in a Sun document, although it was a propos of # JAVA_COMPILER envar settings rather than -Djava.compiler= # property settings, that in the future only the value NONE # would be honored (i.e. disabling JIT) and that the .so-file # basename-suffix semantics of various 1.1.x JDKs would not # hold in the future -- i.e. 1.2.x. Yes you can also use JAVA_COMPILER. I hadn't heard nor seen anything about NONE being legal but I'll check tomorrow when I get back to my copy of the sources. The .so extension is not required for a non-Un*x system which is why you don't add it to the '-Djava.compiler=...' switch. I'm pretty sure the .so extension is hear to stay for all (at least FreeBSD :) Unices for some time to come. # Do you know otherwise? I mean, has your work with the JDK 1.2 # code shown that the reference platform retains the 1.1.x # semantics for JAVA_COMPILER and/or -Djava.compiler=, JavaSoft's # protestations notwithstanding? From what I've seen so far, yes 1.2 uses the same semantics for both the env. variable and the commandline, but I could have overlooked something. I really haven't made it that far yet. I've only just begun to scratch the surface of getting something that doesn't resemble a twisted mess of broken symlinks. :) -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message