Repository navigation
Publish independently built linker inputs - #548
Merged
Merged
Conversation
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.
basic-cli needs PIC-compatible runtime inputs for Roc's upcoming static PIE linker policy. This adds an independent producer and content-addressed release format so those inputs can move out of Git and be reused across platform builds.
The Linker inputs workflow builds PIC musl 1.2.6 and LLVM libunwind for Linux x86-64 and ARM64, plus the existing Windows support archive. A recorded musl startup adjustment supports both older fixed-address executable links and static PIE. Each archive carries source identity, file hashes, provenance, and original licenses. Publication requires successful native checks for all three targets and produces a SHA-256-pinned consumer lock under an immutable prerelease tag.
The Python consumer verifies archive contents and restores inputs through a shared SHA-256 cache. Per-hash locks serialize concurrent downloads, and staged files are closed before publication on Windows.
Validation passed for all three native producers, including Linux function pointers, TLS, threads, fixed-address and PIE startup, and Windows runtime initialization. All five cache/archive regression tests pass. The subsequent platform migration will consume a published lock, enable PIC host builds, and remove the six tracked Linux binaries.