Add nvidia-cuda-{nvrtc, nvcc} as a dependency for cuDF wheels#18686
Add nvidia-cuda-{nvrtc, nvcc} as a dependency for cuDF wheels#18686rapids-bot[bot] merged 7 commits intorapidsai:branch-25.06from
nvidia-cuda-{nvrtc, nvcc} as a dependency for cuDF wheels#18686Conversation
|
Seeing the following error on CI: numba.cuda.cudadrv.driver.LinkerError: [222] Call to cuLinkAddData results in CUDA_ERROR_UNSUPPORTED_PTX_VERSION
ptxas application ptx input, line 9; fatal : Unsupported .version 8.8; current version is '8.7'Looks like cudf/python/cudf/cudf/utils/_numba.py Line 136 in 607200d Not sure what else we are missing |
|
These errors Indicate the PTX is coming from the CUDA 12.9 NVVM library. The version of the nvvm wheel that ends up on the user system cant be newer than the driver it seems. We're probably getting the latest now so that's why it shows up. |
|
reproduced using local CI, following up. |
|
After NVIDIA/numba-cuda#155 are these hard dependencies of numba-cuda? If so, why aren't they part of the dependency list there? If not and that PR is only adding optional support (i.e. the wheels are used if available but other sources are also OK) then should we figure out what we want the final state to be for cudf? I'm fine with making these hard dependencies if we want to say that cudf will always get these libraries from wheels going forward, I just want to make sure that we are aware of the choices we are making if they are not forced upon us by numba-cuda. |
This reverts commit 6b7ffb8.
No, they are not. The current strategy is for the traditional |
|
/merge |
With the merge of NVIDIA/numba-cuda#155 we need to depend on these two wheels if we want
numba-cudato be able to find the runtime libraries it needs in the final cuDF environment.