-
Notifications
You must be signed in to change notification settings - Fork 13k
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
[rustbuild] fix cross compilation of std for mips(el)-linux-musl #32027
Conversation
These targets don't link statically to libunwind or libc
@@ -79,7 +79,7 @@ pub fn check(build: &mut Build) { | |||
} | |||
|
|||
// Make sure musl-root is valid if specified | |||
if target.contains("musl") { | |||
if target.contains("musl") && target.contains("x86_64") { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about i686-unknown-linux-musl
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, we don't provide binaries releases of std for that target (yet). But I guess we probably want to use static linking for that target as well because is not memory constrained like the mips are. @alexcrichton ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, we'd want to use static linking if it worked, but I don't think it would even get past compiling libstd today.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, I'll interpret that as: "let's add i686 here after we confirm we can cross compile std to it using rustbuild".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yes, that was indeed what I intended to convey :)
These targets don't link statically to libunwind or libc --- r? @alexcrichton
These targets don't link statically to libunwind or libc --- r? @alexcrichton
These targets don't link statically to libunwind or libc
r? @alexcrichton