Closed fraidev closed 2 months ago
Fixing the following cross compilation problem:
warning: aws-lc-sys@0.20.1: CMAKE environment variable set: cmake warning: aws-lc-sys@0.20.1: Generating bindings - external bindgen. Platform: armv7-unknown-linux-gnueabihf error: failed to run custom build command for `aws-lc-sys v0.20.1` Caused by: process didn't exit successfully: `/target/release/build/aws-lc-sys-857292f24e7ab0b5/build-script-main` (exit status: 101) --- stdout cargo:rerun-if-env-changed=AWS_LC_SYS_NO_PREFIX cargo:rerun-if-env-changed=AWS_LC_SYS_INTERNAL_BINDGEN cargo:rerun-if-env-changed=AWS_LC_SYS_EXTERNAL_BINDGEN cargo:rerun-if-env-changed=AWS_LC_SYS_NO_ASM cargo:rerun-if-env-changed=AWS_LC_SYS_CMAKE_BUILDER cargo:rerun-if-env-changed=AWS_LC_SYS_STATIC cargo:rerun-if-env-changed=CMAKE cargo:rerun-if-env-changed=CMAKE cargo:warning=CMAKE environment variable set: cmake cargo:warning=Generating bindings - external bindgen. Platform: armv7-unknown-linux-gnueabihf --- stderr Consider installing the bindgen-cli: `cargo install --force --locked bindgen-cli` See our User Guide for more information about bindgen:https://aws.github.io/aws-lc-rs/index.html Failure invoking external bindgen! External bindgen command failed. thread 'main' panicked at /cargo/registry/src/index.crates.io-6f17d22bba15001f/aws-lc-sys-0.20.1/builder/main.rs:469:5: aws-lc-sys build failed. Please enable the 'bindgen' feature on aws-lc-rs or aws-lc-sys.For more information, see the aws-lc-rs User Guide: https://aws.github.io/aws-lc-rs/index.html note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace error: `cross rustc --lib --message-format=json-render-diagnostics --manifest-path Cargo.toml --target armv7-unknown-linux-gnueabihf --release -v --features 'pyo3/abi3-py38 pyo3/extension-module' --crate-type cdylib --` failed with code 101
Also, the cross compilation docker images are old (3 years ago), update them to the latest fix others errors.
Fixing the following cross compilation problem:
Also, the cross compilation docker images are old (3 years ago), update them to the latest fix others errors.