You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Solution to issue cannot be found in the documentation.
I checked the documentation.
Issue
Installing cudatoolkit does not bring with it nvcc or other important utilities. This makes it impossible to use with e.g. CMake's FindCUDAToolkit, which requires nvcc for finding even simple stuff such as the CUDA runtime or driver libraries.
Since, AFAIU, cudatoolkit is being phased one in favour of a new package structure (which does provide nvcc in a new separate package), it would be nice if installing cudatoolkit could print a clear warning message about this. This would be a great service for users, which are currently left in an information vacuum about the situation.
This makes it impossible to use with e.g. CMake's FindCUDAToolkit, which requires nvcc for finding even simple stuff such as the CUDA runtime or driver libraries.
In the other issue, you said that this used to work, but doesn't anymore. Can you elaborate?
I might have misremembered, but I think I used to be able to build Arrow C++ with CUDA enabled a couple years ago using the conda-forge CUDA toolkit.
This is certainly possible as CMake has had multiple big changes to how CUDA is found. cuda-nvcc is a new package and there will be a corresponding cudatoolkit meta-package soon.
I am not sure how useful this is, given that the CUDA 12 rebuild has been performed in many feedstocks and that cudatoolkit is only for CUDA 11 and below. The requested message is equivalent of saying "don't use CUDA 11" on conda-forge. Maybe @conda-forge/cuda folks can share some thoughts?
Solution to issue cannot be found in the documentation.
Issue
Installing
cudatoolkit
does not bring with itnvcc
or other important utilities. This makes it impossible to use with e.g. CMake's FindCUDAToolkit, which requiresnvcc
for finding even simple stuff such as the CUDA runtime or driver libraries.Since, AFAIU,
cudatoolkit
is being phased one in favour of a new package structure (which does providenvcc
in a new separate package), it would be nice if installingcudatoolkit
could print a clear warning message about this. This would be a great service for users, which are currently left in an information vacuum about the situation.Installed packages
Environment info
The text was updated successfully, but these errors were encountered: