-
Notifications
You must be signed in to change notification settings - Fork 83
Open
Description
I am trying to compile libflame with clang/flang. I specify the compilers via environmental variables like this:
CC=mpicc F77=mpifort CFLAGS="-march=znver2 -O3 -DNDEBUG" \
./configure --enable-lapack2flame --enable-dynamic-build --disable-warnings --prefix=${BIN_DIR}/libflame-5.2.0
Compilation used to work just fine, but now I get the error that the command f77
was not found:
$ make
Generating monolithic include/x86_64-unknown-linux-gnu/FLAME.h......................................................................................................................................................................................................................................................................................................................
Generated monolithic include/x86_64-unknown-linux-gnu/FLAME.h
Generating monolithic include/x86_64-unknown-linux-gnu/blis1.h..................
Generated monolithic include/x86_64-unknown-linux-gnu/blis1.h
Generating monolithic include/x86_64-unknown-linux-gnu/FLA_f2c.h...
Generated monolithic include/x86_64-unknown-linux-gnu/FLA_f2c.h
Building src/map/common/lapacksrc/fortran/la_constants.f90
bash: f77: command not found
make: *** [Makefile:610: obj/x86_64-unknown-linux-gnu/src/la_constants.mod] Error 127
I ran a git bisect
session and identified 74b56a2 (#89) as the first bad commit.
It seems like the F77
compiler specified via environmental variables is ignored when building the upstream versions of the LAPACK library. Can you confirm that?
In the meantime, adding the configuration option --enable-legacy-lapack
works as a workaround.
Metadata
Metadata
Assignees
Labels
No labels