Paul -- The output from configure looks ok to me. We're testing for the various capabilities of the fortran compiler that we need, most of which have been around for quite a while. One Big New Thing that isn't around yet is the type(*), dimension(..) notation, which no fortran compiler supports yet. But *most* of the other new MPI-3 Fortran behavior has been around since F2003 (maybe earlier? I'm no expert). (I glossed over a few details here, but you get the point)
Hence, it's not entirely surprising to me that we're determining that an "old" compiler is ok to build the mpi_f08 module. Can you send the output from what happens when you try to build? (or did I miss that in another post?) On Jan 9, 2014, at 7:35 PM, Paul Hargrove <phhargr...@lbl.gov> wrote: > My attempts to build the current 1.7.4rc tarball with versions 8.0 and 9.0 of > the Portland Group compilers fails miserably on compilation of > mpi-f08-types.F90. > > I am sort of surprised by the attempt to build Fortran 2008 support w/ such > old compilers. > I think that fact itself is the real bug here, right? > > With pgi-10.0 I see configure say: > checking if building Fortran 'use mpi' bindings... yes > checking if building Fortran 'use mpi_f08' bindings... no > > But pgi-8.0 and 9.0 both get identified as "good" compilers. > > pgi-9.0: > checking if building Fortran 'use mpi' bindings... yes > checking if Fortran compiler supports BIND(C)... yes > checking if Fortran compiler supports BIND(C) with LOGICAL params... yes > checking if Fortran compiler supports optional arguments... yes > checking if Fortran compiler supports private... no > checking if Fortran compiler supports abstract... yes > checking if Fortran compiler supports asynchronous... no > checking if Fortran compiler supports procedure... no > checking size of Fortran type(test_mpi_handle)... 4 > checking Fortran compiler F08 assumed rank syntax... not cached; checking > checking for Fortran compiler support of TYPE(*), DIMENSION(..)... no > checking Fortran compiler F08 assumed rank syntax... no > checking which mpi_f08 implementation to build... "good" compiler, no array > subsections > configure: WARNING: Temporary development override: forcing the use of F08 > wrappers > checking if building Fortran 'use mpi_f08' bindings... yes > > pgi-8.0 (almost, but not quite, the same): > checking if building Fortran 'use mpi' bindings... yes > checking if Fortran compiler supports BIND(C)... yes > checking if Fortran compiler supports BIND(C) with LOGICAL params... yes > checking if Fortran compiler supports optional arguments... yes > checking if Fortran compiler supports private... no > checking if Fortran compiler supports abstract... no > checking if Fortran compiler supports asynchronous... no > checking if Fortran compiler supports procedure... no > checking size of Fortran type(test_mpi_handle)... 4 > checking Fortran compiler F08 assumed rank syntax... not cached; checking > checking for Fortran compiler support of TYPE(*), DIMENSION(..)... no > checking Fortran compiler F08 assumed rank syntax... no > checking which mpi_f08 implementation to build... "good" compiler, no array > subsections > configure: WARNING: Temporary development override: forcing the use of F08 > wrappers > checking if building Fortran 'use mpi_f08' bindings... yes > > The bzip2-compressed config.log files for pgi-8.0 and 9.0 are attached. > > -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 > <openmpi-1.7-latest-linux-x86_64-pgi-9.0-config.log.bz2><openmpi-1.7-latest-linux-x86_64-pgi-8.0-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/
