You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to compile deal ii on ARCHER2 with LAPACK as a dependency. LAPACK is provided on the system via the cray-libsci module, but even with that module loaded deal ii cannot find LAPACK, even when given the libsci directory.
The relevant cmake flags are -DWITH_LAPACK=ON -DLAPACK_DIR=${CRAY_LIBSCI_PREFIX_DIR}/lib
Cmake is unable to find LAPACK no matter what directory I put into LAPACK_DIR (whether it's the include directory, the parent directory, or lib). It is also unable to find LAPACK if I don't specify any directory and let it search. I imagine it's because the shared library objects in cray-libsci are not named what they're normally named in a standard LAPACK installation, even though the headers are the same.
The text was updated successfully, but these errors were encountered:
Then, deal.II should be able to figure out the library to use.
However, for the AMD optimized libflame which produces lib/libflame.a
I did not have to specify the second option, so maybe just try the first option on a clean build.
I'm trying to compile deal ii on ARCHER2 with LAPACK as a dependency. LAPACK is provided on the system via the cray-libsci module, but even with that module loaded deal ii cannot find LAPACK, even when given the libsci directory.
Logs are below.
CMakeError.log
CMakeOutput.log
The relevant cmake flags are
-DWITH_LAPACK=ON -DLAPACK_DIR=${CRAY_LIBSCI_PREFIX_DIR}/lib
Cmake is unable to find LAPACK no matter what directory I put into LAPACK_DIR (whether it's the include directory, the parent directory, or lib). It is also unable to find LAPACK if I don't specify any directory and let it search. I imagine it's because the shared library objects in cray-libsci are not named what they're normally named in a standard LAPACK installation, even though the headers are the same.
The text was updated successfully, but these errors were encountered: