Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: [OMPI devel] OpenMPI with NAG compiler and gcc 4.6
From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2011-07-11 10:32:37

(moved over from the users list; this is definitely a better fit for the devel list...)

On Jul 11, 2011, at 4:17 AM, Ning Li wrote:

> I am willing to help test OpenMPI with the NAG compiler from time to time but not sure how. If you could give me specific instructions I am very happy to help.

Ping me off the list and I can get you started. The MPI Testing Tool (MTT) is a little complicated to configure, but once you have done so, it can run in a fully automated fashion with little care and feeding required.

> As for this technical issue, I did some research online. It appears that a later version of Libtool (probably 2.2.10+) added support to NAG Fortran compiler. There are discussions at
> The relevant section of code (which I found from Libtool 2.4) looks like:
> nagfor*)
> # NAG Fortran compiler
> _LT_TAGVAR(lt_prog_compiler_wl, $1)='-Wl,-Wl,,'
> _LT_TAGVAR(lt_prog_compiler_pic, $1)='-PIC'
> _LT_TAGVAR(lt_prog_compiler_static, $1)='-Bstatic'
> ;;
> The basic idea here is that nagfor calls gcc (not ld directly) for linking so there are two stages of parameter passing, so the rather strange looking '-Wl,-Wl,,' flag.


OMPI v1.5.x uses Libtool 2.2.6b, unfortunately -- it is highly unlikely that we can upgrade this in the middle of a release series. Indeed, LT made some significant changes after 2.2.6b that would require fairly extensive changes to OMPI v1.5's build system. So upgrading is not likely.

But patching is fine -- we already have several patches in place for various Autotool bugs / back ports. Could you prepare a patch, perchance? OMPI's script applies such patches (our script runs autoconf/automake/etc. -- is only necessary for developers who get SVN checkouts; it's already been run for official OMPI release tarballs). More on patching below.

FWIW, the current OMPI SVN trunk has already been upgraded to LT 2.4; so hypothetically the problem should be fixed there. Could you try a trunk nightly tarball and see if it works with the NAG compiler?

> I can see that in OpenMPI 1.5.3 source, the $OPENMPI_DIR/config/libtool.m4 file does not contain the above code. I have not nuch experience using Libtool so I don't know how to fix this. Simply adding the new code does not seem to work.

It's a little more convoluted, unfortunately. The contents of libtool.m4 are only added to OMPI's "configure" script when "" is run. There's likely a magic place where the patch has to be added in the sequence of events in

If you can find the right place to patch in libtool.m4, try manually editing configure to put the fix in there, too (i.e., you should be able to find enough context from libtool.m4 to find the Right place(s) in configure). If that works, send the libtool.m4 patch along and I can see about putting it in the Right place in

Jeff Squyres
For corporate legal information go to: