From owner-freebsd-java  Mon Feb  2 09:51:39 1998
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA00752
          for java-outgoing; Mon, 2 Feb 1998 09:51:39 -0800 (PST)
          (envelope-from owner-freebsd-java@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA00742
          for <freebsd-java@FreeBSD.ORG>; Mon, 2 Feb 1998 09:51:35 -0800 (PST)
          (envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
	by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA16183;
	Mon, 2 Feb 1998 10:51:32 -0700 (MST)
	(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
	id KAA28000; Mon, 2 Feb 1998 10:51:30 -0700
Date: Mon, 2 Feb 1998 10:51:30 -0700
Message-Id: <199802021751.KAA28000@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Ian Grigg <iang@systemics.com>
Cc: Nate Williams <nate@mt.sri.com>, freebsd-java@FreeBSD.ORG
Subject: Re: jdk115 JNI requires ELF, gcc makes a.out
In-Reply-To: <34D5B297.43856914@systemics.com>
References: <34D531C8.2B6B8D8B@systemics.com>
	<199802020254.TAA26197@mt.sri.com>
	<34D5B297.43856914@systemics.com>
X-Mailer: VM 6.29 under 19.15 XEmacs Lucid
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe java"

> > > 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. :) :)


Nate