Build x86_64-unknown-none libraries with Rust - #632
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
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.
Mere builds its Rust compiler from source, but the standalone x86_64-unknown-none package imports standard libraries built by a different upstream compiler. Those artifacts cannot be consumed by Mere's rustc or reliably live in its immutable sysroot. Build the target libraries as part of the existing Rust toolchain instead, so the compiler and its bare-metal libraries share one build identity and sysroot. Removing the standalone package keeps that incompatible pairing from being selected in future profiles.