From owner-freebsd-java  Mon Feb  2 10:02:13 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA02248
          for java-outgoing; Mon, 2 Feb 1998 10:02:13 -0800 (PST)
          (envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from damon.com (AMAF0bZcRaxvFc+QDt9mk8bAYlbVSwA0@damon.com [207.170.114.1])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02229
          for <freebsd-java@freebsd.org>; Mon, 2 Feb 1998 10:02:09 -0800 (PST)
          (envelope-from dap@damon.com)
Received: (from dap@localhost)
	by damon.com (8.8.7/8.8.7) id MAA06681;
	Mon, 2 Feb 1998 12:01:59 -0600 (CST)
	(envelope-from dap)
From: Damon Permezel <dap@damon.com>
Message-Id: <199802021801.MAA06681@damon.com>
Subject: Re: jdk115 JNI requires ELF, gcc makes a.out
In-Reply-To: <199802021751.KAA28000@mt.sri.com> from Nate Williams at "Feb 2, 98 10:51:30 am"
To: nate@mt.sri.com (Nate Williams)
Date: Mon, 2 Feb 1998 12:01:59 -0600 (CST)
Cc: iang@systemics.com, nate@mt.sri.com, freebsd-java@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"

"Nate Williams sez: "
> > > > However, the result that is produced by gcc is a.out format, and the JVM
> > > > seems to require ELF.
> > > 
> > > Huh?  I don't think so.  FreeBSD doesn't do ELF, so nothing we've
> > > created requires and/or uses ELF.
> > 
> > You're absolutely right, of course, I looked more closely and found I
> > had hooked into the Linux JVM, through some dodgy scripts.  It still
> > doesn't work with the FreeBSD JVM, but I'll have to leave it for now, it
> > looks like some local problem, and I need to fiddle with PATHS.
> 
> *phew*.  OK, when you've got things working, can you let the list know?
> JNI is probably one of the least tested features of the JDK, and it
> would nice to know that it works. :) :)

JNI works....  it was one of the first bugs I ran into.

I am certainly interested in any counter examples.