-
Notifications
You must be signed in to change notification settings - Fork 504
Invalid summary version when compiling zkvm guest #2250
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
Comments
@storopoli and @Rajil1213 have also encountered this issue on macOS by using llvm@20 from brew and fixed by installing llvm@19. I have 19 installed but not functional. Guessing it's not choosing it for some reason or another. |
Can you do the following checks:
|
I'm using Bazzite which is immutable, so
Going to try uninstall from brew and install llvm10 into rpm-ostree and see what happens. |
I have exactly these lines in my # Fuck you C/C++
export CFLAGS="-I/opt/homebrew/include"
export LDFLAGS="-L/opt/homebrew/lib"
# Fuck you WASM32
#export PATH="/opt/homebrew/opt/llvm/bin:$PATH"
# Workaround for strata-bridge, fuck you sp1
export PATH="/opt/homebrew/opt/llvm@19/bin:$PATH" I had to install Don't forget to nuke all nested # Rust
if command -v fd &> /dev/null; then
cleanrust() {
fd -It d -g target -X rm -rf
}
fi |
@Zk2u Do you still have issues with llvm? |
As far as I remember, yes. I'll follow up in a few days as I don't have access to my machine ATM. |
I've switched to a non immutable fedora and with llvm installed via DNF, working fine. Doesn't solve this issue though |
Component
sp1-zkvm
Have you ensured that all of these are up to date?
What version of SP1 SDK are you on?
4.1.3
What version of the cargo prove CLI are you on?
cargo-prove sp1 (9312c7c 2025-04-17T18:45:11.033695524Z)
Operating System
Linux (Other)
Describe the bug
I get a
rust-lld: error: Invalid summary version 12. Version should be in the range [1-10]
running on Bazzite (fedora) 42. Rust installed via rustup. Clang installed via rpm-ostree, sp1 installed from sp1up.The text was updated successfully, but these errors were encountered: