I have a question about the Open MPI 1.10.2 provided by PGI with 17.1. Namely, does it require installation in a certain path?
For example, the admins here installed PGI 17.1 in
(and 2017 of course) and the compiler seemed okay. I then whipped up a module to point to the Open MPI included because I was lazy and didn’t want to build it like I usually do (built-in!).
I then went to try and build some libraries. When I got to NCO, it threw:
PGC/x86-64 Linux 17.1-0: compilation completed with warnings libtool: link: ranlib .libs/libnco.a /bin/sed: can't read /proj/pgi/linux86-64/2017/mpi/openmpi-1.10.2/lib/libmpi.la: No such file or directory libtool: link: `/proj/pgi/linux86-64/2017/mpi/openmpi-1.10.2/lib/libmpi.la' is not a valid libtool archive make: *** [libnco.la] Error 1 make: *** Waiting for unfinished jobs....
I’ll have to stare a bit more, but I’m wondering if it’s reading, say, lib/pkgconfig/ompi.pc and seeing:
which might tell it that is where Open MPI lives. That is not the prefix we installed under, so I can see some issues.
Is this a new requirement/request from PGI for us to build in /proj to use Open MPI? I looked at the installation guide and says that /opt/pgi is still the default, but should we try /proj/pgi if we want to use the built-in MPI? Or, is this something I should bring up with the NCO devels (and I’ll admit the NCO I’m building isn’t the very latest, I tend to be cautious upgrading it until necessary).[/code]