-
-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
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
Unsupported cuda toolkit version: 12.8
. Please raise a github issue.
#324
Comments
Came here to report this too |
It would be nice if the error reported the latest supported Cuda version so people would know what to downgrade to. |
I think it's cuda-12060 based on the feature flags |
12060 does link to 12.8 without any issues but, specifically calls the version 12.6 in the build.rs PR created here |
@coreylowman support for 12.8 would be amazing! |
Released on v0.13.5 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
PS C:...\Desktop\codes\gpu_test> cargo run
Downloaded libloading v0.8.6
Downloaded cudarc v0.13.4
Downloaded 2 crates (1.8 MB) in 2.09s (largest was
cudarc
at 1.8 MB)Compiling windows_x86_64_msvc v0.52.6
Compiling cudarc v0.13.4
error: failed to run custom build command for
cudarc v0.13.4
Caused by:
process didn't exit successfully:
C:\...\Desktop\codes\gpu_test\target\debug\build\cudarc-47af9edca483256a\build-script-build
(exit code: 101)--- stdout
cargo:rerun-if-changed=build.rs
cargo:rerun-if-env-changed=CUDA_ROOT
cargo:rerun-if-env-changed=CUDA_PATH
cargo:rerun-if-env-changed=CUDA_TOOLKIT_ROOT_DIR
--- stderr
thread 'main' panicked at C:....cargo\registry\src\index.crates.io-6f17d22bba15001f\cudarc-0.13.4\build.rs:85:14:
Unsupported cuda toolkit version:
12.8
. Please raise a github issue.note: run with
RUST_BACKTRACE=1
environment variable to display a backtraceCargo.toml:
[package]
name = "gpu_test"
version = "0.1.0"
edition = "2021"
[dependencies]
cudarc = { version = "0.13.4", features = ["cuda-version-from-build-system"] }
The text was updated successfully, but these errors were encountered: