Skip to content

configure: Do not generate two stage0 rustlib dirs when --libdir is set #31074

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

Merged
merged 1 commit into from Jan 22, 2016
Merged

configure: Do not generate two stage0 rustlib dirs when --libdir is set #31074

merged 1 commit into from Jan 22, 2016

Conversation

ghost
Copy link

@ghost ghost commented Jan 21, 2016

This fixes #27254.

On a 64-bit Linux machine, for example, configure --libdir=/usr/local/lib64 was creating both x86_64-unknown-linux-gnu/stage0/lib/rustlib and x86_64-unknown-linux-gnu/stage0/lib64/rustlib. Crates from the stage0 snapshot, like libcore, are extracted to x86_64-unknown-linux-gnu/stage0/lib/rustlib, but the stage0 compiler was attempting to find them in x86_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.

@rust-highfive
Copy link
Contributor

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

@alexcrichton
Copy link
Member

@bors: r+ 6aa86e5

Thanks!

@bors
Copy link
Collaborator

bors commented Jan 22, 2016

⌛ Testing commit 6aa86e5 with merge cd1b845...

bors added a commit that referenced this pull request Jan 22, 2016
This fixes #27254.

On a 64-bit Linux machine, for example, `configure --libdir=/usr/local/lib64` was creating both `x86_64-unknown-linux-gnu/stage0/lib/rustlib` and `x86_64-unknown-linux-gnu/stage0/lib64/rustlib`. Crates from the stage0 snapshot, like `libcore`, are extracted to `x86_64-unknown-linux-gnu/stage0/lib/rustlib`, but the stage0 compiler was attempting to find them in `x86_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.
@bors bors merged commit 6aa86e5 into rust-lang:master Jan 22, 2016
@ghost ghost deleted the stage0-libdir branch January 22, 2016 11:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Setting --libdir breaks rustc build
4 participants