-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LUMI port: Compile with Cray compiler suite #10
Comments
jamesavery
added a commit
that referenced
this issue
Nov 10, 2023
…ewrote to slightly less nice (1,element) vector constructor
jamesavery
added a commit
that referenced
this issue
Nov 10, 2023
…Disabling for now, since they are only used in Fortran program. But figure out later how to fix.
jamesavery
added a commit
that referenced
this issue
Nov 10, 2023
…rs just ignore it). But it breaks Cray compilation on LUMI, as C++17 disallows it. Buckygen is soooo messily written!
jamesavery
added a commit
that referenced
this issue
Nov 10, 2023
…ions were causing trouble with Cray CC. Moved to header to avoid the need.
jamesavery
added a commit
that referenced
this issue
Nov 10, 2023
… Now sets CMAKE_Fortran_LINK_EXECUTABLE, so linking works. Everything CPU-only now compiles on LUMI!
Now everything builds and runs. Last TODO before closing issue: sanity checks on results. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, the CMake setup is very GCC/GFortran-centric, with some GNU options hardcoded. This breaks compiles on LUMI, which uses the Cray Compiler Environment (CCE).
Need to clean up the CMakeList.txt to not assume GNU compilers (also useful for compiling on clang-based mac systems).
The text was updated successfully, but these errors were encountered: