-
Notifications
You must be signed in to change notification settings - Fork 576
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
Error with boost-core hash when building with F40 #1228
Comments
Update: But then I instantly ran into another hash error:
Something is seriously wrong here. Why are these sha512 hashes all wrong!? |
WTF!? According to The correct hash for
|
We're aware of this issue. Here are more details microsoft/vcpkg#38974. The gist is that boost changed files on their servers breaking all boost vcpkg ports. You should be able to checkout the latest vcpkg commit and update
|
Closing this since it was fixed by #1229 |
Current Behavior
I'm trying to build Cemu on a Fedora 40 system via my fedora cemu podman project:
https://github.com/leifliddy/podman-cemu-builder
but there's an issue with downloading https://github.com/boostorg/core/archive/boost-1.85.0.tar.gz
**The issue doesn't just affect F40 -- the exact same error occurs when building with F39.
This issue should be super easy to replicate via my project.
I'm seeing this in the
vcpkg-manifest-install.log
If I run the following:
I get the following hash on that file
a1e774c98b537dd42018742af68f5889af1afd4e6c9809399987124e56a3b9ae2f20e8173170bc6fc0ad76fb95e2da7b9d385a4037e9ee12011fc02bf8f7e009
Why does it think the hash should be
3a7be75e52f5c20830fccb9e7391a1e4556ebb072e6324df95b1ba38bed46e24f4c9f27a62a1099eddc90f2ac1ede083f0c850e2dc27fd42375d028516f675b3
??Expected Behavior
The file hashes should match.
Steps to Reproduce
Run my project -- to build Cemu with Fedora 40
https://github.com/leifliddy/podman-cemu-builder
System Info (Optional)
OS: Fedora 40
GPU: Radeon RX XT/7900
Emulation Settings (Optional)
No response
Logs (Optional)
The text was updated successfully, but these errors were encountered: