Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update linux_musl base to dynamically link the crt by default #133386

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

wesleywiser
Copy link
Member

However, don't change the behavior of any existing targets at this time. For targets that used the old default, explicitly set crt_static_default = true.

This makes it easier for new targets to use the correct defaults while leaving the changing of individual targets to future PRs.

Related to rust-lang/compiler-team#422

However, don't change the behavior of any existing targets at this time.
For targets that used the old default, explicitly set `crt_static_default = true`.

This makes it easier for new targets to use the correct defaults while
leaving the changing of individual targets to future PRs.

Related to rust-lang/compiler-team#422
@rustbot
Copy link
Collaborator

rustbot commented Nov 23, 2024

r? @BoxyUwU

rustbot has assigned @BoxyUwU.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Nov 23, 2024
@rustbot
Copy link
Collaborator

rustbot commented Nov 23, 2024

These commits modify compiler targets.
(See the Target Tier Policy.)

Comment on lines -11 to -13
// These targets statically link libc by default
base.crt_static_default = true;

Copy link
Member

@jieyouxu jieyouxu Nov 23, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question: do we have any way to test (or rather, track) the "finalized" crt static default for each target (as in, after the base and overrides are merged together to produce the final value for a given target)? So that if anyone does modify the default and cause the "finalized" value to change, we do so intentionally with something like a test rebless or test modification?

I looked at --print=all-target-specs-json locally, but AFAICT that omits this field if it's not overriden or something...

@BoxyUwU
Copy link
Member

BoxyUwU commented Nov 23, 2024

r? @jieyouxu

@rustbot rustbot assigned jieyouxu and unassigned BoxyUwU Nov 23, 2024
@jieyouxu jieyouxu added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Nov 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants