The following is NOT a bug report. This is just an observation that may deserve some text in the README.
I've reported issues in the past with some Fortran compilers (mostly older XLC and PGI) which either cannot build the "use mpi_f08" module, or cannot correctly link to it (and sometimes this fails only if configured with --enable-debug). Testing the OSHMEM Fortran bindings (enabled by default on Linux) I have found several compilers which fail to link the examples (hello_oshmemfh and ring_oshmemfh). I reported one specific instance (with xlc-11/xlf-13) back in February: http://www.open-mpi.org/community/lists/devel/2014/02/14057.php So far I have these failures only on platforms where the Fortran compiler is *known* to be broken for the MPI f90 and/or f08 bindings. Specifically, all the failing platforms are ones on which either: + Configure determines (without my help) that FC cannot build the F90 and/or F08 modules. OR + I must pass --enable-mpi-fortran=usempi or --enable-mpi-fortran=mpifh for cases configure cannot detect. So, I do *not* believe there is anything wrong with the OSHMEM code, which is why I started this post with "The following is NOT a bug report". However, I have two recommendations to make: 1) Documentation The README says just: --disable-oshmem-fortran Disable building only the Fortran OSHMEM bindings. So, I recommend adding a sentence there referencing the "Compiler Notes" section of the README which has details on some known bad Fortran compilers. 2) Configure: As I noted above, at least some of the failures are on platforms where configure has determined it cannot build the f08 MPI bindings. So, maybe there is something that could be done at configure time to disqualify some Fortran compilers from building the OSHMEM fotran bindings, too. -Paul -- Paul H. Hargrove phhargr...@lbl.gov Future Technologies Group Computer and Data Sciences Department Tel: +1-510-495-2352 Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
