-
Notifications
You must be signed in to change notification settings - Fork 16
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
IBM z/Architecture (s390x) support #139
Comments
Maybe it would be possible to build with ring and openssl, not with rusttls... You could do a quick test by replacing rusttls with openssl-sys inside of all our crates. Do something hackish, like changing all the |
@flavio I removed rustls from all crates and I could compile kwctl on s390x. I also had to remove mdcat because it was using rustls.
I tried to use wasmtime 0.33.0 to see if this issue was fixed. For that I used wasmtime-provider v1.0.0-alpha.0, then I got this error:
Anyway it looks like relocation S390xPCRel32Dbl is still not implemented https://github.com/bytecodealliance/wasmtime/blob/main/crates/cranelift/src/obj.rs#L439 |
Ouch, thanks a lot for the investigation. This is useful information |
Signed-off-by: Cintia Sanchez Garcia <cynthiasg@icloud.com>
I got an error with the ring crate when compiling kwctl for s390x. It is the same error described here briansmith/ring#986
I get the same error compiling ring on a s390x VM and cross compiling with
cargo build --target s390x-unknown-linux-gnu
.musl does not work on s390x,
cargo build --target s390x-unknown-linux-musl
fails because std is not available https://doc.rust-lang.org/nightly/rustc/platform-support.html#tier-3This PR briansmith/ring#1297 adds support for s390x, but it looks like it's not in active development and needs more work. I successfully compiled ring from this PR on s390x, but rustls does not compile because there were some changes done in ring 0.17. I got the following error:
I can compile kwctl if I remove rustls, then the following error is deployed when executing
kwctl run
Summary of what we would need:
The text was updated successfully, but these errors were encountered: