Repository navigation
Keep the static variants' toolchains in gcroots too - #17
Merged
Merged
Conversation
thomasjm
force-pushed
the
gcroots-static
branch
from
October 16, 2026 01:29
c5d1423 to
99bfbc0
Compare
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
1 participant
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.
gcrootsnamed only the five dynamic variants, so the musl cross GHCs weren't retained — and those are the ones built from source. The artifacts it also names don't help: a cross GHC is a build-time dependency, not a runtime reference of the binary it produced.Switches to every entry in
allVersions, static included, so new variants are covered without editing the list.