Repository navigation
Use x86_64 GCC build on aarch64 Windows hosts - #604
Closed
SergioGasquez wants to merge 2 commits into
Closed
SergioGasquez wants to merge 2 commits into
SergioGasquez wants to merge 2 commits into
Conversation
Member
Author
|
Closed for #605 |
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.
Fixes GCC installation on
aarch64-pc-windows-msvchosts, which fails withHTTP GET Error: 404 Not Found.#601 mapped ARM64 Windows hosts to the
aarch64-w64-mingw32GCC artifact, but #602 reverted the default GCC toesp-15.2.0_20250920, which only shipsx86_64andi686Windows builds. Only the20260609+ crosstool-NG releases shipaarch64-w64-mingw32.This uses the
x86_64-w64-mingw32build on ARM64 Windows, which runs emulated. LLVM already does the same, and this works with any--crosstool-toolchain-version.