From owner-freebsd-java Thu Feb 14 11: 7:23 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 C707E37B400 for ; Thu, 14 Feb 2002 11:07:21 -0800 (PST) Received: from billh by gnuppy.monkey.org with local (Exim 3.34 #1 (Debian)) id 16bRDw-0000Nt-00; Thu, 14 Feb 2002 11:07:16 -0800 Date: Thu, 14 Feb 2002 11:07:16 -0800 To: Guerry Semones Cc: freebsd-java@FreeBSD.ORG Subject: Re: Need info for compiling JDK1.3.1 on FreeBSD with Native Threads Message-ID: <20020214190716.GA1472@gnuppy.monkey.org> References: <200202141202.AA308543714@mail.mstar2.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200202141202.AA308543714@mail.mstar2.net> User-Agent: Mutt/1.3.27i 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 Thu, Feb 14, 2002 at 12:02:08PM -0700, Guerry Semones wrote: > We are initializing the JVM *in* the C++ code using > JNI_CreateJavaVM. The code runs fine on Windows 2000 with > JDK1.3.1. We are porting to FreeBSD. Which means nothing since Win32 has different things happening within it. You can't just call that function without initializing the environment the JVM lives in (mmaps, threading, weak symbol resolution) which is why the JVM should be started first and then some kind of native method is used to initialize your C++ program, run it, etc... The JVM environment should be the program driving the coexisting program. I mean, what did you expect ? ;-) bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message