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
Hello everyone,
ascent_execution_policies.hpp only defines the struct CudaExec if Raja is enabled (ASCENT_RAJA_ENABLED). But ascent_dispatch.hpp requires CudaExec if CUDA is enabled (ASCENT_CUDA_ENABLED) which is independent of Raja.
This results in the build error:
cd easybuild_obj/libs/ascent && bin/nvcc -forward-unknown-to-host-compiler -ccbin=bin/g++ -DASCENT_EXPORTS_FLAG -DVTKMDIY_MPI_AS_LIB -DVTKMDIY_NO_THREADS -Dascent_EXPORTS -IPython/3.10.4-GCCcore-11.3.0/include/python3.10 -Iascent/src/thirdparty_builtin/lodepng -Iascent/src/thirdparty_builtin/tiny_obj -Iascent/src/libs -Ieasybuild_obj/libs/ascent -Iascent/src/libs/ascent -Iascent/src/libs/ascent/c -Iascent/src/libs/ascent/utils -Iascent/src/libs/ascent/runtimes -Iascent/src/libs/ascent/hola -Iascent/src/libs/ascent/runtimes/flow_filters -IConduit/0.8.8-GCCcore-11.3.0/lib/python3.10/site-packages/conduit -Iascent/src/libs/flow -Iascent/src/libs/flow/filters -Ieasybuild_obj/libs/flow -Ieasybuild_obj/libs -I/p/software/jusuf/stages/2023/software/CUDA/11.7/include -Iascent/src/libs/rover -Ieasybuild_obj/libs/rover -isystem=VTKm/2.0.0-GCCcore-11.3.0/include/vtkm-2.0/vtkm/thirdparty/lcl/vtkmlcl -isystem=VTKm/2.0.0-GCCcore-11.3.0/include/vtkm-2.0/vtkm/thirdparty/diy/vtkmdiy/include -isystem=Conduit/0.8.8-GCCcore-11.3.0/include/conduit -isystem=VTKm/2.0.0-GCCcore-11.3.0/include/vtkm-2.0/vtkm/thirdparty/optionparser -isystem=VTKm/2.0.0-GCCcore-11.3.0/include/vtkm-2.0/vtkm/thirdparty/diy -isystem=VTKm/2.0.0-GCCcore-11.3.0/include/vtkm-2.0/vtkm/thirdparty/diy/vtkmdiy/include/vtkmdiy/mpi -isystem=VTKm/2.0.0-GCCcore-11.3.0/include/vtkm-2.0 -Xnvlink=--suppress-stack-size-warning --expt-extended-lambda --expt-relaxed-constexpr -Xptxas --disable-optimizer-constants -O3 -DNDEBUG -Xcompiler=-fPIC -Xcompiler=-ffunction-sections --expt-relaxed-constexpr -Xcompiler=-fopenmp -std=c++14 -MD -MT libs/ascent/CMakeFiles/ascent.dir/runtimes/expressions/ascent_blueprint_architect.cpp.o -MF CMakeFiles/ascent.dir/runtimes/expressions/ascent_blueprint_architect.cpp.o.d -x cu -rdc=true -c ascent/src/libs/ascent/runtimes/expressions/ascent_blueprint_architect.cpp -o CMakeFiles/ascent.dir/runtimes/expressions/ascent_blueprint_architect.cpp.o ascent/src/libs/ascent/runtimes/expressions/ascent_dispatch.hpp(275): error: identifier "CudaExec" is undefined
The text was updated successfully, but these errors were encountered:
Hi @jhgoebbert
Thanks for this report and pointing to the root cause -- we had another build failure / symptom that I think was caused by this issue.
We will get this resolved.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Hello everyone,
ascent_execution_policies.hpp only defines the struct CudaExec if Raja is enabled (ASCENT_RAJA_ENABLED).
But ascent_dispatch.hpp requires CudaExec if CUDA is enabled (ASCENT_CUDA_ENABLED) which is independent of Raja.
This results in the build error:
The text was updated successfully, but these errors were encountered: