{{ message }}
Repository navigation
cargo-lambda reqwest & cargos needing ring #647
Answered
by
miikka
DoIevenLift
asked this question in
Q&A
Replies: 1 comment 1 reply
|
Based on your screenshot, the problem is in compiling OpenSSL, not ring. What happens is that Cargo is trying to use OpenSSL from the system ( openssl = { version = "0.10", features = ["vendored"] }This is essentially the same thing that cargo tree --target aarch64-unknown-linux-gnu |
1 reply
Answer selected by
DoIevenLift
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Based on your screenshot, the problem is in compiling OpenSSL, not ring. What happens is that Cargo is trying to use OpenSSL from the system (
openssl-sys) package, but that won't work with cross-compiling. One solution is to use vendored OpenSSL by adding the following line to your dependencies:This is essentially the same thing that
native-tls-vendoredends up doing, and that's also why it stops working when you remove it. If you want to understand why OpenSSL (or ring) gets included in the dependency tree, you can usecargo treeto inspect it: