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
{{ message }}
This repository has been archived by the owner on Oct 21, 2022. It is now read-only.
So this code block should check if the environment variables have a valid value, and if not, pass on to the remainder of the function to check the nvcc path and the default system paths.
The text was updated successfully, but these errors were encountered:
No, it was pure bad luck on my part -- my .bashrc file happens to set CUDA_PATH to something meaningful if I'm on a system where I know in advance that CUDA is installed, and (apparently) to an empty variable if not. On the system where I was running when I ran into this, I hadn't yet told this script where CUDA is installed on that system.
If I have
CUDA_PATH
in my environment but set as an empty variable, CUDA discovery will fail.In this case,
find_toolkit()
will return an empty list. This will then fail infind_toolkit_version()
when building the CUDAnative package:The problem is that the code that checks if these env vars exist will return immediately even if the env vars are empty:
https://github.com/JuliaGPU/CUDAapi.jl/blob/v1.0.1/src/discovery.jl#L230-L241
So this code block should check if the environment variables have a valid value, and if not, pass on to the remainder of the function to check the nvcc path and the default system paths.
The text was updated successfully, but these errors were encountered: