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

Using --enable-local-rust causes stage1 and stage2 binaries to be linked with system rust #21344

Closed
tdaede opened this issue Jan 18, 2015 · 3 comments
Labels
A-linkage Area: linking into static, shared libraries and binaries

Comments

@tdaede
Copy link
Contributor

tdaede commented Jan 18, 2015

I am attempting to use a system install of rust (from binary form) as the stage0 of a local rust build. I need to do this because stage0 snapshots are not available for my architecture. When I do this using --enable-local-rust, the stage1 and stage2 rustc binaries end up being linked with system shared libraries, e.g. the original stage0 snapshot binaries. This causes them not to work due to missing symbols.

@mneumann
Copy link
Contributor

I think I hit the same problem on DragonFly!

@kmcallister kmcallister added A-linkage Area: linking into static, shared libraries and binaries A-build labels Jan 18, 2015
@steveklabnik
Copy link
Member

Triage: I am not sure if anything has changed here or not. @tdaede have you still seen this recently?

@alexcrichton
Copy link
Member

Make's now gone, so closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-linkage Area: linking into static, shared libraries and binaries
Projects
None yet
Development

No branches or pull requests

5 participants