linking problems with jar files

Mon Feb 7 11:48:00 GMT 2005

I tried to do that, but it looks like that didn't work -
java.lang.System still didn't have the mapLibraryName() method that I
need for JNI. It's just that the particular build I have is a bit old
so there's no method implementation. It's not a big deal anyway as I
planned to use CNI whenever possible. I'm sure if I had a more recent
build, the method's implementation would be there.
-Vijay 
-----Original Message-----
From: tromey@redhat.com [mailto:tromey@redhat.com] 
Sent: Thursday, February 03, 2005 10:45 AM
To: Prabhakar, Vijay (IT)
Cc: java@gcc.gnu.org
Subject: Re: linking problems with jar files
>>>>> "Vijay" == Prabhakar, Vijay (IT)
<Vijay.Prabhakar@morganstanley.com> writes:
Vijay> That was one of the things I was considering doing. I'd prefer 
Vijay> not to unpackage the jar and rip out some of the guts - basically
Vijay> it comes down to some of the classes using JNI and needing 
Vijay> java.lang.System.loadLibrary(). My build is 3.2.3-42 and that 
Vijay> particular method wasn't implemented afaik.
I'm pretty sure System.loadLibrary and JNI both were in 3.2. Try
compiling with '-fjni'.
Tom 
--------------------------------------------------------

NOTICE: If received in error, please destroy and notify sender. Sender does not waive confidentiality or privilege, and use is prohibited. 