-
Notifications
You must be signed in to change notification settings - Fork 105
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 mrustc 0.9 to bootstrap rust 1.29.0 directly #140
Comments
What is the output of the following command:
I once got a similar error with my rustc backend when that ar file was corrupted, so that only one object file was readable. |
|
That doesn't seem to be the problem. |
Might be related to #138 - there's some funnies with library link order. |
Hmm, how could dtolnay see the linker command that is executed? |
The linker command comes from the |
The linker command that fails is:
|
Moving "-l" "ssh2" to immediately after "-l" "git2" manually makes it work just fine. |
This seems familiar; I encountered a similar issue here; my assumption, as noted in that comment, is this is due to a change in linker behavior:
|
Closing in favor of #138 |
Hi,
so we are progressing nicely to update Rust bootstrapping packages in Guix.
Right now, I'm trying to switch from mrustc 0.9 bootstrapping rust 1.19.0 to mrustc 0.9 bootstrapping rust 1.29.0 directly.
With that, I get the following error messages when building rust 1.29.0's cargo (rust 1.29.0's rustc builds fine) [for comparison: using the same method, rust 1.19.0's rustc and cargo build fine]:
Have you seen that before?
The text was updated successfully, but these errors were encountered: