Sorry to hear you spent the day dealing with both fortran and autoconf.
I spent mine dealing with my auto insurance company claims department.
So, we both had miserable days but you win.
The 1.7 tarball was ready by the time I read your message and I've launched
a flock of testers.
Were there any specific platforms/configurations you want me to retest
tonight w/ 1.7?
After the 1.7 tests on the XLF, Open64 and PathScale platforms complete
I'll be testing the trunk on those systems with the compiler-appropriate
I might eventually see about refining the PGI good/nogood table by desired
level of fortran support.
However, there is no point in doing that until the churn has ended.
On Wed, Jan 22, 2014 at 6:41 PM, Jeff Squyres (jsquyres) <jsquyres_at_[hidden]
> Ok, here's my update: I fixed a bunch of issues in the Fortran support
> today; most are minor, but they took a while to verify (and some are slated
> for v1.7.5 because they aren't critical). I also added the ability to
> disable building the mpi_f08 module.
> Here's what's on the trunk / v1.7, and will be in nightly tarballs soon
> (v1.7 is building now; I have to re-start the trunk one when v1.7 finishes
> because I goofed and it failed the first time):
> - Fix for MPI_STATUS_IGNORE issue (a side-effect of the "protected" update
> the other day)
> - Add some missing interfaces for MPI_Neighbor subroutines
> - Add missing interfaces for the profiled versions of the MPI_Dist_graph
> - Add missing pre-defined function callbacks in the mpi_f08 module
> Here's what's on the trunk and still awaiting a code review (probably
> tomorrow) before it can go to v1.7:
> - --enable-mpi-fortran behavior now allows you specify up to what level of
> Fortran bindings you want built:
> --enable-mpi-fortran: tries to build them all (this is the default)
> --enable-mpi-fortran=mpifh: only builds mpif.h support
> --enable-mpi-fortran=usempi: builds mpif.h and use mpi support
> --enable-mpi-fortran=usempif08: builds mpif.h, use mpi, and use mpi_f08
> --disable-mpi-fortran: does not build any Fortran support
> So to disable the mpi_f08 bindings, you can --enable-mpi-fortran=usempi.
> On Jan 22, 2014, at 5:45 PM, Jeff Squyres (jsquyres) <jsquyres_at_[hidden]>
> > Update: I've been working all day on Fortran issues (pulling on one
> Paul-Fortran--sweater-thread revealed several other issues :-( ).
> > I'll be sending an update soon...
> > On Jan 22, 2014, at 5:40 PM, Paul Hargrove <phhargrove_at_[hidden]> wrote:
> >> On Wed, Jan 22, 2014 at 1:33 PM, Ralph Castain <rhc_at_[hidden]>
> >> My main concern with 1.7.4 at the moment stems from all the Fortran
> changes we pushed into that release - this occurred *after* 1.7.3, and so
> those problems represent a regression in the 1.7 series.
> >> Unless I am missing something, the currently open Fortan issues are:
> >> + XLF, which didn't work in 1.7.3 either (just verified this today)
> >> + PathScale and Open64 which fail building in
> >> The XLF issue is not a regression.
> >> The remaining PathScale/Open64 issue MAY be a compiler bug.
> >> If Jeff follows through on his promise to implement
> --disable-mpi-fortran-08 then use of that option is a work-around for the
> regression on PathScale and Open64.
> >> -Paul
> >> --
> >> Paul H. Hargrove PHHargrove_at_[hidden]
> >> 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
> >> devel_at_[hidden]
> >> http://www.open-mpi.org/mailman/listinfo.cgi/devel
> > --
> > Jeff Squyres
> > jsquyres_at_[hidden]
> > For corporate legal information go to:
> > _______________________________________________
> > devel mailing list
> > devel_at_[hidden]
> > http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Jeff Squyres
> For corporate legal information go to:
> devel mailing list
Paul H. Hargrove PHHargrove_at_[hidden]
Future Technologies Group
Computer and Data Sciences Department Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory Fax: +1-510-486-6900