NAG Fortran compiler -rpath configuration error

[nncarlson]

With NAG 6.0, 6.1 and openmpi 2.1.1, mpifort gives the error

gcc: error: unrecognized command line option ‘-rpath’

This may have been part of #1284 (now closed). If it was ever fixed, it is back now. The issue is that the compiler wrapper uses -Wl,-rpath which results in -rpath being passed to gcc. In order to get that flag to the linker, the wrapper must use -Wl,-Wl,,-rpath. See http://baradi09.blogspot.com/2014/08/compiling-openmpi-with-nag-fortran.html

[nncarlson]

Actually there are several -Wl, options in mpifort and I suspect they may all be wrong for the same reason.

[ggouaillardet]

@nncarlson thanks for the report.

this is a known issue that has been around for a while ...
i fixed that some time ago, but then my NAG evaluation license has expired and the related commits were never backported into the v2 branches.

can you please give a try to v3.0.0rc2 ?
(the fixes were backported into this branch)

if you'd rather use the v2.1 series, you can manually download the patch at https://github.com/open-mpi/ompi/pull/2092.patch, and apply it.
note you need recent autotools, and then you will have to run ./autogen.sh --force

[nncarlson]

@ggouaillardet sorry it took me so long to give this a try.

I downloaded v3.0.0rc2 and ran ./autogen.pl (no .sh) -- that seemed to go fine. I was then able to successfully build and use this version, so I'd say your fixes are spot on.

Out of curiosity when is 3.0.0 due to be released?

[ggouaillardet]

@nncarlson did you get a chance to try the patch at https://github.com/open-mpi/ompi/pull/2092.patch on the v2.x branch ? once this gets tested, i will do my best to have it included in the next v2.1.1 release.

v3.0.0 is due anytime now ... once we can solve the remaining blocking issues

[nncarlson]

@ggouaillardet I've tested the patch now, and it too looks good to me. It applied cleanly to 2.1.1 with some offsets/fuzzes. Ran autogen.pl --force and then configure as usual. This also fixes the problem I reported in #4032.