Ah, I see. Yes, this is what we originally thought was a Pathscale bug, but it later turned out that Pathscale was correct and MPI-3.0 was wrong (which led to a major errata for the mpi_f08 stuff :-( ).
Meaning: Fortran explicitly says that BIND(C) is not compatible with LOGICAL dummy params (which is why we took much BIND(C) usage out in an MPI-3 errata). Hence, this configure test is not correct; the answer should *always* be "no" (even though most compilers allow it!). Therefore, this litmus test is no good -- we need some another one. Possibilities: 1. Check for BIND(C) name support of > 32 characters 2. Somehow check for the internal compiler errors #1 is a little tricky because of ABI issues, but is do-able (although I'm not happy about it...). #2 will truly suck; I don't know what causes the internal error. By definition, it's a compiler bug, and I really don't want to have to test for compiler bugs in a configure test. :-( It could be that #1 is sufficient. I'm still waiting to hear back from Pathscale. On Jan 22, 2014, at 11:02 PM, Paul Hargrove <phhargr...@lbl.gov> wrote: > The reason appears to be: > checking if Fortran compiler supports BIND(C) with LOGICAL params... no > > The requested files are attached. > > -Paul > > > On Wed, Jan 22, 2014 at 7:46 PM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> > wrote: > Can you send me the configure output and config.log from this build? I'd > like to see why it chose not to build the mpi_f08 module. > > > On Jan 22, 2014, at 10:08 PM, Paul Hargrove <phhargr...@lbl.gov> wrote: > > > > > On Wed, Jan 22, 2014 at 6:31 PM, Jeff Squyres (jsquyres) > > <jsquy...@cisco.com> wrote: > > But just to confirm: you said that your pathscale compilers *do* compile > > 1.7.3 -- including the mpi_f08 module -- with no problems? That would be a > > little surprising, because those same >=32 character symbol names are in > > 1.7.3... > > > > Not quite - I was a bit too quick in composing that email. > > The mpi_f08 stuff is NOT getting built in 1.7.3 when using pathf95. > > What I should have said is "the fortran code and configure script in 1.7.3 > > work together to produce a failure-free build". > > > > $ bin/ompi_info | grep -e Ident -e Fort > > Ident string: 1.7.3 > > Fort mpif.h: yes (all) > > Fort use mpi: yes (full: ignore TKR) > > Fort use mpi size: deprecated-ompi-info-value > > Fort use mpi_f08: no > > Fort mpi_f08 compliance: The mpi_f08 module was not built > > Fort mpi_f08 subarrays: no > > Fort compiler: pathf95 > > Fort compiler abs: > > /project/projectdirs/ftg/ekopath-4.0.12.1/bin/pathf95 > > Fort ignore TKR: yes (!DIR$ IGNORE_TKR) > > Fort 08 assumed shape: no > > Fort optional args: no > > Fort BIND(C): yes > > Fort PRIVATE: no > > Fort ABSTRACT: no > > Fort ASYNCHRONOUS: no > > Fort PROCEDURE: no > > Fort f08 using wrappers: yes > > Fort mpif.h profiling: yes > > Fort use mpi profiling: yes > > Fort use mpi_f08 prof: no > > > > -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 > > _______________________________________________ > > devel mailing list > > de...@open-mpi.org > > http://www.open-mpi.org/mailman/listinfo.cgi/devel > > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > _______________________________________________ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel > > > > -- > 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 > <configure.stdout.bz2><config.log.bz2>_______________________________________________ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
