We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
While building julia with USE_BINARYBUILDER=0, the llvm tarball fetched is llvm-julia-16.0.6-2.tar.gz, and it failed the checksum check.
USE_BINARYBUILDER=0
llvm-julia-16.0.6-2.tar.gz
the deps/checksums/llvm has been updated by #53195, and the downloaded file currently match the previous hash.
deps/checksums/llvm
I am unsure if:
Cc @gbaraldi and @vchuravy who worked on the llvm update
The text was updated successfully, but these errors were encountered:
The source hash should not have changed. Since https://github.com/JuliaLang/llvm-project/tags is still on 16.0.6-2 and 16.0.6+4 was a pure build change in Yggdrasil. I am unsure why contrib/update_checksums messed that up.
contrib/update_checksums
Sorry, something went wrong.
We can't build the source distribution tarballs for v1.11.0-alpha1 because of this as they require USE_BINARYBUILDER=0.
Revert change to checksum for llvm-julia
4718e57
Should fix JuliaLang#53399. I think this is the correct fix.
Revert change to checksum for llvm-julia (#53870)
b2e8eb2
Should fix #53399. I think this is the correct fix. Makes it so you can build Julia with `USE_BINARYBUILDER=0`.
6f8e78d
Should fix #53399. I think this is the correct fix. Makes it so you can build Julia with `USE_BINARYBUILDER=0`. (cherry picked from commit b2e8eb2)
gbaraldi
Successfully merging a pull request may close this issue.
While building julia with
USE_BINARYBUILDER=0
, the llvm tarball fetched isllvm-julia-16.0.6-2.tar.gz
, and it failed the checksum check.the
deps/checksums/llvm
has been updated by #53195, and the downloaded file currently match the previous hash.I am unsure if:
Cc @gbaraldi and @vchuravy who worked on the llvm update
The text was updated successfully, but these errors were encountered: