Just a follow-up. RPATH was the trouble. All is well now in the land
of the climatologists again. Thanks again for the help.
Ray
On 6/12/2015 8:00 AM, Ray Sheppard wrote:
Thanks again Gilles,
You might be on to something. Dynamic libraries sound like
some
Thanks again Gilles,
You might be on to something. Dynamic libraries sound like something
a Python developer might love (no offense intended to the stereotype).
It would also explain why the build went smoothly but the test run
crashed. I am going to try putting an RPATH variable in the env
Ray,
one possibility is one of the loaded library was built with -rpath and this
causes the mess
an other option is you have to link _error.so with libmpi.so
Cheers,
Gilles
On Friday, June 12, 2015, Ray Sheppard wrote:
> Hi Gilles,
> Thanks for the reply. I completely forgot that lived in
Hi Gilles,
Thanks for the reply. I completely forgot that lived in the main
library. ldd doesn't show that it read my LD_LIBRARY_PATH (I also push
out an LPATH variable just for fun). I force modules to echoed when
users initialize them. You can see OpenMPI was visible to H5py. Now I
won
Ray,
this symbol is defined in libmpi.so.
can you run
ldd
/N/dc2/projects/ray/quarry/h5py/h5py-2.5.0/build/lib.linux-x86_64-2.7/h5py/_errors.so
and make sure this is linked with openmpi 1.8.4 ?
Cheers,
Gilles
On 6/12/2015 1:29 AM, Ray Sheppard wrote:
Hi List,
I know I saw this issue year
