bootstrap: always propagate CARGO_TARGET_{host}_LINKER#152077
Merged
Conversation
We were already setting `CARGO_TARGET_{target}_LINKER` when there is a
setting in `bootstrap.toml`, and when the host and target are the same,
this is also used for build scripts and proc-macros.
However, the host value wasn't set when building for any other target,
and Cargo would see that as a fingerprint change for those build
artifacts, rebuilding them.
If we always set the `CARGO_TARGET_{host}_LINKER`, then those build
scripts will keep a consistent Cargo fingerprint, so they'll remain
cached no matter how we're alternating targets.
rustbot
added
S-waiting-on-review
Collaborator
|
rustbot has assigned @Mark-Simulacrum. Use |
Member
|
@bors r+ rollup=iffy |
Contributor
rust-bors
Bot
added
S-waiting-on-bors
JonathanBrouwer
added a commit
to JonathanBrouwer/rust
that referenced
this pull request
Feb 8, 2026
…ark-Simulacrum
bootstrap: always propagate `CARGO_TARGET_{host}_LINKER`
We were already setting `CARGO_TARGET_{target}_LINKER` when there is a
setting in `bootstrap.toml`, and when the host and target are the same,
this is also used for build scripts and proc-macros.
However, the host value wasn't set when building for any other target,
and Cargo would see that as a fingerprint change for those build
artifacts, rebuilding them.
If we always set the `CARGO_TARGET_{host}_LINKER`, then those build
scripts will keep a consistent Cargo fingerprint, so they'll remain
cached no matter how we're alternating targets.
This was referenced Feb 8, 2026
rust-bors Bot
pushed a commit
that referenced
this pull request
Feb 8, 2026
…uwer Rollup of 5 pull requests Successful merges: - #151869 (add test for codegen of SIMD vector from array repeat) - #152077 (bootstrap: always propagate `CARGO_TARGET_{host}_LINKER`) - #126100 (Reword the caveats on `array::map`) - #152275 (Stop having two different alignment constants) - #152325 (Remove more adhoc groups that correspond to teams)
rust-timer
added a commit
that referenced
this pull request
Feb 9, 2026
Rollup merge of #152077 - cuviper:bootstrap-host-linker, r=Mark-Simulacrum bootstrap: always propagate `CARGO_TARGET_{host}_LINKER` We were already setting `CARGO_TARGET_{target}_LINKER` when there is a setting in `bootstrap.toml`, and when the host and target are the same, this is also used for build scripts and proc-macros. However, the host value wasn't set when building for any other target, and Cargo would see that as a fingerprint change for those build artifacts, rebuilding them. If we always set the `CARGO_TARGET_{host}_LINKER`, then those build scripts will keep a consistent Cargo fingerprint, so they'll remain cached no matter how we're alternating targets.
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
3 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.
We were already setting
CARGO_TARGET_{target}_LINKERwhen there is asetting in
bootstrap.toml, and when the host and target are the same,this is also used for build scripts and proc-macros.
However, the host value wasn't set when building for any other target,
and Cargo would see that as a fingerprint change for those build
artifacts, rebuilding them.
If we always set the
CARGO_TARGET_{host}_LINKER, then those buildscripts will keep a consistent Cargo fingerprint, so they'll remain
cached no matter how we're alternating targets.