Open imreallyliam opened 3 years ago
It appears your Sodium layer doesn't work with arm64 via cross-compilation, on my pi, I was able to compile Libsodium.
EDIT: included CC
process didn't exit successfully: `/home/removed/packetcrypt_rs/target/release/build/packetcrypt-sys-cb1857f72f9301b7/build-script-build` (exit status: 101) --- stdout Looking for libsodium in /home/removed/packetcrypt_rs/target/aarch64-unknown-linux-gnu/release/build Found sodium.h in /home/removed/packetcrypt_rs/target/aarch64-unknown-linux-gnu/release/build/libsodium-sys-aefa16d2d6a25e4a/out/source/libsodium/src/libsodium/include TARGET = Some("aarch64-unknown-linux-gnu") HOST = Some("x86_64-unknown-linux-gnu") CC_aarch64-unknown-linux-gnu = None CC_aarch64_unknown_linux_gnu = None TARGET_CC = None CC = None CROSS_COMPILE = None CFLAGS_aarch64-unknown-linux-gnu = None CFLAGS_aarch64_unknown_linux_gnu = None TARGET_CFLAGS = None CFLAGS = None CRATE_CC_NO_DEFAULTS = None CARGO_CFG_TARGET_FEATURE = None --- stderr thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { kind: IOError, message: "No such file or directory (os error 2)" }', packetcrypt-sys/build.rs:101:42 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace warning: build failed, waiting for other jobs to finish... error: build failed```
you was able to compile?
Only on the pi itself
@xeu100 please share the steps or something
It's the same steps, but you do it on the pi itself.
It appears your Sodium layer doesn't work with arm64 via cross-compilation, on my pi, I was able to compile Libsodium.
EDIT: included CC