ET fails to compile on BlueWaters due to failure to detect F90 compiler
Issue #2274
resolved
A recent change to the flesh configure code to detect a F90 compiler makes the code fail on BW with
checking whether the Fortran compiler (ftn -g3 -m128bit-long-double -fcray-pointer -ffixed-line-length-none ) works... yes checking whether the Fortran compiler (ftn -g3 -m128bit-long-double -fcray-pointer -ffixed-line-length-none ) is a cross-compiler... yes configure: error: Could not run executable generated by Fortran compiler (see configs/sim/config-data/config.log for details). If this is a cross configuration please set CROSS_COMPILE=yes. Error reconfiguring sim-config make: *** [sim-config] Error 2
and config.log contains
configure:2025: checking whether the Fortran compiler (ftn -g3 -m128bit-long-double -fcray-pointer -ffixed-line-length-none ) works configure:2040: ftn -o conftest conftest.f 1>&5 ./conftest: error while loading shared libraries: libacml.so: cannot open shared object file: No such file or directory configure:2069: checking whether the Fortran compiler (ftn -g3 -m128bit-long-double -fcray-pointer -ffixed-line-length-none ) is a cross-compiler
which indicates something off with the acml library we request for BW.
Comments (3)
-
reporter -
reporter - changed status to open
-
reporter - changed status to resolved
- Log in to comment
This requires both a fix to simfactory’s option list ad92d56 "bluewaters: add -Wl,--rpath flags to F77 and F90 flags" in simfactory2 as well as a change to the flesh fixing a bug in the commit to
#1111. Pull request is https://bitbucket.org/cactuscode/cactus/pull-requests/63/rhaas-f77flags/diff .Please review.