Repository navigation
chore: fall back to the toolchain mirror for public downloads - #276
Merged
Merged
Conversation
setup.sh and the compiler build scripts try lombyte-project/toolchain-mirror (pinned to a commit) when an upstream download fails: binutils, objdiff, the EE GCC source, gcc-2.95.2, bison 1.28 and the GCC 2.95.2 headers. Same SHA-256 pins as before.
Decompilation progress
No function changed its match state compared with main (a23dc98). Compared with main (a23dc98). C_FUZZY uses main's last measurement. |
setup.sh stops with 'could not download' instead of a misleading hash error, and a failed sparse checkout of the SDK headers also falls back to the toolchain mirror.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Before
Every open-source toolchain file came from one upstream link. If that link went away (the EE GCC source already lives only on archive.org), setup stopped.
After
lombyte-project/toolchain-mirror keeps a copy of each open-source file with its license and source, and explains the toolchain choices. When an upstream download fails, the setup tries the mirror, pinned to a commit:
setup.sh: binutils, objdiff, and the GCC 2.95.2 headers (when the SDK mirror clone or checkout fails). When both fail, setup stops with "could not download" instead of a hash error.scripts/build-game-compiler.py: the EE GCC 991111b source, bison 1.28scripts/build-sn-compiler.py: gcc-2.95.2docs/build/building.md: one line about the mirrorThe SHA-256 pins are the same. Sony's and SN's binaries are not in the mirror; setup still fetches them from their public sources.
Verification
scripts/test_public_tools.pypasses in CI (tools).make elfnot rerun.