-
Notifications
You must be signed in to change notification settings - Fork 50
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
Does the cmake build work with clang? #3645
Comments
In general, I would suggest specifying compilers via environment variables, not inside the cmake options, when using cmake directly:
Does this make a difference for your build? Edit:
|
As I have multiple mpi installs besides the system-wide one with gcc, e.g., with clang, I usually point cmake to non-system mpi wrappers via either env vars (as you suggest) or via cmake's args. Neither of the above helps though with the error if I have clang behind the mpi wrappers. (Though, I'm also happy with the workaround in #3646.) |
That is interesting. Could you please paste the complete |
https://gist.github.com/jbakosi/a827cbdcab0d3bcfdc4df5874703d4e9 It only errors with |
@matthiasdiener @ebohm I have a couple of colleagues here at AMD who are trying to get Charm++ built with our clang-based AOCC compiler and are snagging in the same error described here. Do you guys have an ETA for a fix on this issue? |
I'm guessing if gfortran is not installed, CMake will blank out Side note, if you're using mpicc and mpicxx, I would set the Fortran compiler to mpif90 or similar. |
I usually do, but for cmake projects that do not enable fortran, this remains an issue. |
On debian linux, I do
and I get
Seems like a command is missing in charmc:236
Does someone have a workaround?
The text was updated successfully, but these errors were encountered: