-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Provide rust-lld on s390x (for the wasm target) #94324
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
Comments
I believe we don't build lld for most non-x86 hosts, though I don't see any particular issue with including it. I think all it would take is an
|
Yep, if CI passes with it added it's generally fine to do so for tier 2 with host tools targets (or better), though it may get removed if it causes undue CI time burden (unlikely). |
Thanks for the comments! Would you like me to submit a PR adding the |
Normally, you'd be able to verify using rust/src/ci/docker/host-x86_64/dist-aarch64-linux/Dockerfile Lines 1 to 14 in 4b043fa
|
OK, I'll give it a try. As an aside, Ubuntu 20.04 contains a full cross-toolchain targeting s390x out of the box, so I'm not sure we'd really need crosstool-ng at all - unless there's a particular reason the Rust build requires it? However, if we update this to Ubuntu 20.04, would this have the side effect that the generated Rust toolchains would no longer install on older distros? We really don't want that. |
Trying to build for the
wasm32-unknown-unknown
target on a s390x host fails with:This seems to be because - unlike on other architectures -
rust-lld
is not built and packaged as part of the rust toolchain.Now, it is true that LLD currently does not support the s390x architecture. But that is only an issue when trying to use the s390x architecture as target - it is completely fine to build LLD on a s390x host and use it to link binaries for any other target architecture it supports, in particular including wasm.
Would it be possible to include
rust-lld
on s390x as well, to make building wasm binaries more straightforward?The text was updated successfully, but these errors were encountered: