Open jeffhammond opened 8 years ago
Can you give us more information about your system (OS, compiler, ...) so that we can reproduce this error?
It's my CentOS 6.5 Linux workstation. I can give you an account if you want to verify, although I have already fixed my issues by hand-modifying the compiler wrappers and adding symbolic links from libshmem_pmi to libshmem.
...although libshmem isn't used by the wrapper. Because LD_LIBRARY_PATH
doesn't include the SHMEM library paths, I do a static link.
If you don't install within the system search paths for dynamic libraries then you have to add the install path to LD_LIBRARY_PATH. This is true for any library. It's fine if you prefer static linking to dynamic linking. I think you've just wandered into an area we have not tested in a while. We'll add it to our to-do list.
The reason that libshmem works for you is because PRK is adding "-lshmem" to the linker command. You should really remove "-lshmem" from LDLIBS in the SHMEM/Makefile and ask users to provide the build magic for their SHMEM library under common/Make.defs.
If you don't install within the system search paths for dynamic libraries then you have to add the install path to LD_LIBRARY_PATH. This is true for any library. It's fine if you prefer static linking to dynamic linking. I think you've just wandered into an area we have not tested in a while. We'll add it to our to-do list.
I don't see any reason to not create rpath binaries. MPICH supports this, at least as an option.
I'll add rpath feature and file PR later. You need not address it.
The reason that libshmem works for you is because PRK is adding "-lshmem" to the linker command.
It actually doesn't help. Symbolic links just cause it to fail another way. You should really remove "-lshmem"
Agreed. from LDLIBS in the SHMEM/Makefile and ask users to provide the build magic for their SHMEM library under common/Make.defs.
Yeah we don't have enough magic yet ;-)
If I try to build a static binary,
oshcc
fails due to not knowing where Pthreads is...