configure: Do not generate two stage0 rustlib dirs when --libdir is set #31074
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.
This fixes #27254.
On a 64-bit Linux machine, for example,
configure --libdir=/usr/local/lib64
was creating bothx86_64-unknown-linux-gnu/stage0/lib/rustlib
andx86_64-unknown-linux-gnu/stage0/lib64/rustlib
. Crates from the stage0 snapshot, likelibcore
, are extracted tox86_64-unknown-linux-gnu/stage0/lib/rustlib
, but the stage0 compiler was attempting to find them inx86_64-unknown-linux-gnu/stage0/lib64/rustlib
, which has the highest priority on a 64-bit system.The issue can be fixed by creating only
x86_64-unknown-linux-gnu/stage0/lib/rustlib
, since this is the only rustlib directory needed for stage0 anyways.