Paul -- I'm sorry, due to craziness and the holiday yesterday, the amended Fortran BIND(C) checks didn't get committed to the v1.7 branch until earlier today. So they'll be in tonight's tarball.
It looks to me like the Open64 compilers won't pass the BIND(C) checks, and we should be ok. Can you verify tonight? As for adding --disable-mpi-fortran-08... maybe. I'd still prefer the configure script to just Do The Right Thing. But I see your point for handling the one-off cases where it doesn't. On Jan 17, 2014, at 7:49 PM, Paul Hargrove <phhargr...@lbl.gov> wrote: > Building the v1.7 tarball (1.7.4rc2r30303) with AMD's Open64 compilers > (v4.5.2) I hit the errors shown in the attached make.log (too long to > cut-and-paste). > I've also attached config.log and configure's stdout. > > "We don't care about that compiler" is an acceptable (to me) answer, but I am > reporting this for completeness. > > Jeff may need to do more work on the configure probes for F08 support. > OR, why not provide --disable-mpi-f08 ? > > -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 > <configure.stdout.bz2><config.log.bz2><make.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/
