Closed liqi16 closed 6 months ago
Hi! Could you specify what command was run?
It appears to be coming from pasta-msm
dependency. Do you have nvcc and other tools to be able to build pasta-msm?
Perhaps, worth compiling it in portable feature? cargo build --features "portable"
Another thing to try might be to clone pasta-msm and try to build it?
Thank you for your kind response! @srinathsetty
I run the cargo test --release
command. When it processed the nova-snark(test), it reported this error.
Building [=======================> ] 265/266: nova-snark(test)
I have nvcc
, but I met another error when I tried to build pasta-msm. (Sorry, I am a beginner in ZK and Rust) Also, when I tried to use the cargo build --features "portable"
command, I met the same error. Does that mean my CUDA version is too low? How can I solve this problem when I don't have permission to upgrade CUDA?
I am looking forward to hearing back from you. Thank you very much.
$ nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2019 NVIDIA Corporation
Built on Sun_Jul_28_19:07:16_PDT_2019
Cuda compilation tools, release 10.1, V10.1.243
error: failed to run custom build command for `sppark v0.1.5`
Caused by:
process didn't exit successfully: `/home/lq/project/Nova/target/debug/build/sppark-90441368c7869e69/build-script-build` (exit status: 101)
--- stdout
cargo:ROOT=/home/lq/.cargo/registry/src/index.crates.io-6f17d22bba15001f/sppark-0.1.5/sppark
--- stderr
thread 'main' panicked at /home/lq/.cargo/registry/src/index.crates.io-6f17d22bba15001f/sppark-0.1.5/build.rs:67:13:
Unsupported CUDA version 10.1 < 11.4
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
Hi @liqi16. I've been unable to reproduce this issue as I don't have a machine with a GPU that matches what you are using. I think this is coming from the pasta-msm crate in your environment. I think the easiest would be to check the following.
cargo bench
I suspect this will fail in your environment. If it fails, could you please open an issue in their repository? If it succeeds, please reopen this issue here.
When I tried this command: cargo test --release, I met this error. How can I solve it?