I searched around, and I can’t for the life of me see where all that cruft is coming from. Any suggestions?
Here is the top of the config.log from that build: This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by ompi-ibm configure 10.0, which was generated by GNU Autoconf 2.69. Invocation command line was $ ./configure CC=mpicc CXX=mpic++ F77=mpif77 ## --------- ## ## Platform. ## ## --------- ## hostname = bend001 uname -m = x86_64 uname -r = 3.10.0-229.7.2.el7.x86_64 uname -s = Linux uname -v = #1 SMP Tue Jun 23 22:06:11 UTC 2015 Do you want to see the log itself? I’m at a loss as to why it would add that stuff. > On Sep 12, 2015, at 7:38 AM, Ralph Castain <r...@open-mpi.org> wrote: > > Note that I didn’t set any of those flags outside of the CC and friends - > they are being set by our MTT test configure itself. The compiler is just gcc > 4.8.3, and I suspect O5 is asking a bit from it. > > >> On Sep 12, 2015, at 6:08 AM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> >> wrote: >> >> I notice that your configure line in the MTT tests is this: >> >> CC=cc CXX=CC FC=f90 F77=f77 --with-wrapper-cflags="-xtarget=opteron >> -xprefetch -xprefetch_level=2 >> -xvector=simd,lib -xdepend=yes -xbuiltin=%all -xarch=amd64a -xO5" >> CFLAGS="-xtarget=opteron >> -xprefetch -xprefetch_level=2 -xvector=simd,lib -xdepend=yes -xbuiltin=%all >> -xarch=amd64a -xO5" >> --with-wrapper-cxxflags="-xtarget=opteron -xprefetch -xprefetch_level=2 >> -xvector=simd,lib >> -xdepend=yes -xbuiltin=%all -xarch=amd64a -xO5" CXXFLAGS="-xtarget=opteron >> -xprefetch >> -xprefetch_level=2 -xvector=simd,lib -xdepend=yes -xbuiltin=%all >> -xarch=amd64a -xO5" >> --with-wrapper-fflags="-xtarget=opteron -xprefetch -xprefetch_level=2 >> -xvector=simd,lib -stackvar >> -xarch=amd64a -xO5" FFLAGS="-xtarget=opteron -xprefetch -xprefetch_level=2 >> -xvector=simd,lib >> -stackvar -xarch=amd64a -xO5" --with-wrapper-fcflags="-xtarget=opteron >> -xprefetch -xprefetch_level=2 >> -xvector=simd,lib -stackvar -xarch=amd64a -xO5" FCFLAGS="-xtarget=opteron >> -xprefetch >> -xprefetch_level=2 -xvector=simd,lib -stackvar -xarch=amd64a -xO5" >> >> What compiler suite is that? Is -xO5 really safe to use? >> >> >> >>> On Sep 11, 2015, at 8:51 PM, Ralph Castain <r...@open-mpi.org> wrote: >>> >>> Hi folks >>> >>> I’ve closed all the holes I can find in the PMIx integration, and things >>> look pretty good overall. There are a handful of failures still being seen >>> - most of them involving what appear to be unrelated code. I’m not entirely >>> sure I understand the source of the errors, and could really use some help >>> to determine (a) if these are in any way related to PMIx, and if so (b) how. >>> >>> The errors from my MTT run are here: >>> http://mtt.open-mpi.org/index.php?do_redir=2256 >>> >>> Any help diagnosing these problems would be greatly appreciated >>> Ralph >>> >>> _______________________________________________ >>> devel mailing list >>> de...@open-mpi.org >>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel >>> Link to this post: >>> http://www.open-mpi.org/community/lists/devel/2015/09/18013.php >> >> >> -- >> 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 >> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel >> Link to this post: >> http://www.open-mpi.org/community/lists/devel/2015/09/18018.php >
