|Re: Workaround for Bug 139064 on Linux (JNI: UnsatisfiedLinkError)? [message #649000 is a reply to message #648796]
||Mon, 17 January 2011 07:55
| Benjamin Bihler
Registered: July 2009
|Marco Maccaferri wrote on Fri, 14 January 2011 09:26|
I'm running with 64bit Linux, I don't know if it makes any difference.
About the libraries, the first is a third-party library compiled with
its own setup (standard Linux toolchain, compiled with the classic
../configure make commands). The jni library is compiled with Eclipse CDT
with roughly the default settings (the command is g++ -O3 -Wall -c
-fmessage-length=0 -fPIC -MMD -MP). Linker is also standard, no more
than g++ -shared.
I do not see any substantial difference here. My libraries are compiled with
g++ --shared -fPIC ...
and the executable is linked with
so that the library dependencies can be resolved.
On the other hand: are there many programmers loading native libraries with dependencies in eclipse fragments? If this worked, the bug mentioned in my first message would not be marked as "NEW" but as "SOLVED" instead, right?! Sad, sad...
Powered by FUDForum
. Page generated in 0.05954 seconds