-
Notifications
You must be signed in to change notification settings - Fork 696
Fix compilation on aarch64-unknown-linux-musl #912
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
Conversation
Didn't build on FreeBSD due to ENOSPC. If you push again, I think it'll build. Or, you can bypass bors and just press the merge button, just this once. |
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.
LGTM.
Hi Gents, are you planning to merge this? It would be very helpful for us - we are trying to build on aarch64-musl and stuck on this one. |
@agend while this fixes nix now, it's likely this will break again in the future. If you really want to get proper support added to nix, please contribute to japaric/cross as we rely on that for our CI testing. bors r+ |
912: Fix compilation on aarch64-unknown-linux-musl r=Susurrus a=Susurrus trust/cross don't support this architecture, so it's non-trivial to add CI testing for this to nix, but this fixed it locally for me. Since it's not a supported platform, I haven't added anything to the CHANGELOG, since this could break before the next release. Co-authored-by: Bryant Mairs <[email protected]>
Build failed |
bors r+ |
912: Fix compilation on aarch64-unknown-linux-musl r=Susurrus a=Susurrus trust/cross don't support this architecture, so it's non-trivial to add CI testing for this to nix, but this fixed it locally for me. Since it's not a supported platform, I haven't added anything to the CHANGELOG, since this could break before the next release. Co-authored-by: Bryant Mairs <[email protected]>
@@ -48,7 +48,7 @@ libc_bitflags!{ | |||
/// Put the mapping into the first 2GB of the process address space. | |||
#[cfg(any(all(any(target_os = "android", target_os = "linux"), | |||
any(target_arch = "x86", target_arch = "x86_64")), | |||
all(target_os = "linux", target_env = "musl", any(target_arch = "x86", target_pointer_width = "64")), | |||
all(target_os = "linux", target_env = "musl", any(target_arch = "x86", target_arch = "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.
Emm, isn't this branch
all(target_os = "linux", target_env = "musl", any(target_arch = "x86", target_arch = "x86_64"))
already covered by
all(any(target_os = "android", target_os = "linux"), any(target_arch = "x86", target_arch = "x86_64"))
trust/cross don't support this architecture, so it's non-trivial to add CI testing for this to nix, but this fixed it locally for me. Since it's not a supported platform, I haven't added anything to the CHANGELOG, since this could break before the next release.