Michael Schellenberger Costa
Michael Schellenberger Costa
I see that we use `--cuda-path=/usr/local/cuda` in the invocation could it be that it overrides the include folders?
Looks like it is indeed not looking at the right directories https://github.com/NVIDIA/cccl/actions/runs/19306545198/job/55215540328?pr=6592#step:4:736 We are missing the `/usr/lib/llvm-20/include/c++/v1/` include path
If I build locally I get: > #include "..." search starts here: #include search starts here: /home/coder/cccl/libcudacxx/include /usr/lib/llvm-20/lib/clang/20/include/cuda_wrappers /usr/lib/llvm-20/bin/../include/c++/v1 /usr/lib/llvm-20/lib/clang/20/include /usr/local/include /usr/include/x86_64-linux-gnu /usr/include /usr/local/cuda/include
Its build here: https://github.com/rapidsai/devcontainers/actions/runs/19273329169/job/55123065290
🥇 https://github.com/rapidsai/devcontainers/actions/runs/19273329169/job/55123065162#step:7:9268
I believe that removal is a red hering, somethign else is going on
Oh no I found it, its our clang-format install 😢 https://github.com/rapidsai/devcontainers/actions/runs/19273329169/job/55123065162#step:7:8482
I am super puzzled, I verified that the devxontainers now have libc++ inside
it fails for both arm and amd64, so its not dependent on that
We love our unsupported compiler thingy https://github.com/NVIDIA/cccl/actions/runs/18144608121/job/51643523655?pr=6083#step:4:533 I dont know how we can circumvent that for CMAKE