Date: Sun, 1 Feb 1998 19:54:46 -0700 From: Nate Williams <nate@mt.sri.com> To: Ian Grigg <iang@systemics.com> Cc: freebsd-java@FreeBSD.ORG Subject: Re: jdk115 JNI requires ELF, gcc makes a.out Message-ID: <199802020254.TAA26197@mt.sri.com> In-Reply-To: <34D531C8.2B6B8D8B@systemics.com> References: <34D531C8.2B6B8D8B@systemics.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> I've been using your FreeBSD JDK 1.1.5, and it hums. I've compiled up > and tested all of the current Cryptix distribution, and it went through > with no problems. Cool. There are still some gotchas to track down, but for the most part it seems to work. > I'm now trying something harder: Cryptix-C Native (JNI). I've got it to > compile ok, with only this change: > > cd bin; ln -s i386 i586 > > which was required for javah. Weird? They are doing something non-portable. > 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. If the Cryptix-C stuff in JNI, do they provide you with C sources and/or libraries? If libraries, are *they* ELF compiled? If so, then they are not for FreeBSD, but for Solaris and/or Linux, and will not work under FreeBSD. (That's why they call it Java *NATIVE* Interface, which means it's not portable across architectures/OS's.) In short, the current JDK requires everything to be 100% Pure and/or compiled for FreeBSD in the case of the JNI stuff. Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199802020254.TAA26197>