We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Using build_ascent_hip_frontier.sh on frontier, it looks like some part of vtkm isn't properly including mpi:
build_ascent_hip_frontier.sh
[...]/ascent/scripts/build_ascent/source/vtk-m-v2.1.0/vtkm/filter/flow/internal/BoundsMap.h:25:10: fatal error: 'mpi.h' file not found
If I force the include with export CPATH=/opt/cray/pe/mpich/8.1.28/ofi/crayclang/17.0/include/ it passes this point.
export CPATH=/opt/cray/pe/mpich/8.1.28/ofi/crayclang/17.0/include/
The text was updated successfully, but these errors were encountered:
When compiling with the cray compilers, they know where MPI exists.
However, in VTK-m, the compile drops to only use amdclang++ to compile device code and it does not know about implicit mpi paths.
The fix is to add the MPI include path to general includes, we can add this to the frontier script.
Sorry, something went wrong.
@mlohry
Where you trying the latest script, we do have some logic to address this:
ascent/scripts/build_ascent/build_ascent_hip_frontier.sh
Line 16 in 10b1253
@cyrush yes I used the latest and I see that line there, odd that it didn't work.
No branches or pull requests
Using
build_ascent_hip_frontier.sh
on frontier, it looks like some part of vtkm isn't properly including mpi:If I force the include with
export CPATH=/opt/cray/pe/mpich/8.1.28/ofi/crayclang/17.0/include/
it passes this point.The text was updated successfully, but these errors were encountered: