Thanks Kihwal! This was an excellent suggestion and worked great!
Should have the Java bindings out shortly...
On Jan 31, 2012, at 4:35 PM, Kihwal Lee wrote:
> There might be other tricks you can play with CL, but here is my idea: You
> could have the initial jni native lib to become a sort of
There might be other tricks you can play with CL, but here is my idea: You
could have the initial jni native lib to become a sort of wrapper to dlopen()
the real thing (the one plug-ins depend on) with RTLD_GLOBAL, so that the fact
that the jni library is loaded in a specific name space does not
I was able to dig further into this, and we believe we finally tracked this
down to root cause. It appears that java loads things into a private, as
opposed to global, namespace. Thus, the Java MPI bindings load the initial
libmpi just fine.
However, when libmpi then attempts to load the indivi
Managed to get this to work - had to adjust our configure a little (one setting
artificially introduced a different path). Thanks!
On Jan 30, 2012, at 5:13 PM, Kihwal Lee wrote:
> It doesn't have to be static.
> Do architectures match between the node manager jvm and the library?
> If one is 32
On Jan 30, 2012, at 5:13 PM, Kihwal Lee wrote:
> It doesn't have to be static.
> Do architectures match between the node manager jvm and the library?
> If one is 32 bit and the other is 64, it won't work.
That's a good question - I'll check...
>
> Kihwal
>
> On 1/30/12 5:58 PM, "Ralph Castain
On Jan 30, 2012, at 3:58 PM, Ralph Castain wrote:
> I have tried setting -Djava.library.path and LD_LIBRARY_PATH to the correct
> locations. In both cases, I get errors from the JNI code indicating that it
> was unable to open the specified dynamic library.
Do the paths to OpenMPI libraries, a
It doesn't have to be static.
Do architectures match between the node manager jvm and the library?
If one is 32 bit and the other is 64, it won't work.
Kihwal
On 1/30/12 5:58 PM, "Ralph Castain" wrote:
Hi folks
As per earlier emails, I'm just about ready to release the Java MPI bindings. I
ha
Hi folks
As per earlier emails, I'm just about ready to release the Java MPI bindings. I
have one remaining issue and would appreciate some help.
We typically build OpenMPI dynamically. For the Java bindings, this means that
the JNI code underlying the Java binding must dynamically load OMPI p
