-
Notifications
You must be signed in to change notification settings - Fork 385
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
use runner setting specified in Cross.toml #500
Conversation
bors r+ |
497: don't set RUSTFLAGS in aarch64-musl image r=reitermarkus a=japaric instead use a linker wrapper to work around issue rust-lang/rust#46651 not setting RUSTFLAGS inside the container lets end users pass rustc flags via `.cargo/config` this is an alternative to #464 that doesn't require bumping the MSRV of the `aarch64-unknown-linux-musl` target (that is the aarch64-musl image will continue to work with Rust 1.42 where bug rust-lang/rust#46651 is still presen ) 500: use runner setting specified in Cross.toml r=reitermarkus a=japaric fixes #499 Co-authored-by: Jorge Aparicio <jorge.aparicio@ferrous-systems.com>
Build failed (retrying...): |
Build failed: |
bors r+ |
Build failed: |
it seems that the debian sysroot that's used by the dropbear: error while loading shared libraries: libtomcrypt.so.1: cannot open shared object file: No such file or directory
[ 2.593663] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
[ 2.593663]
[ 2.594109] CPU: 2 PID: 1 Comm: dropbear Not tainted 4.19.0-11-arm64 #1 Debian 4.19.146-1
[ 2.594255] Hardware name: linux,dummy-virt (DT)
[ 2.595546] Call trace: |
35ec4e1
to
99c2ac6
Compare
last two commits should fix this |
bors r+ |
Build succeeded: |
fixes #499