Replace RUST_LIBC_UNSTABLE env with libc_unstable* cfg#4977
Draft
tgross35 wants to merge 2 commits intorust-lang:mainfrom
Draft
Replace RUST_LIBC_UNSTABLE env with libc_unstable* cfg#4977tgross35 wants to merge 2 commits intorust-lang:mainfrom
RUST_LIBC_UNSTABLE env with libc_unstable* cfg#4977tgross35 wants to merge 2 commits intorust-lang:mainfrom
Conversation
The internal config `linux_time_bits64` already gets set via the musl or glibc config, so it isn't useful to be able to set it on its own. Delete the env option since it isn't used anyway.
tgross35
force-pushed
the
libc-cfg
branch
2 times, most recently
from
adfca8d to
3d160eb
Compare
Make it easier to set these flags only for host or target, not both. This was discussed on Zulip.
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
2 participants
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.
Make it easier to set these flags only for specific targets, and not necessarily on the host. This was discussed on Zulip.