Some RUSTFLAGS Force Cargo Use on the Host #903
Description
Checklist
- I've looked through the issues and pull requests for similar reports
Describe your issue
Attempting to run the following causes cross to assume that we do not need docker support, and therefore fallback to the host:
$ CARGO_TARGET_AARCH64_UNKNOWN_LINUX_GNU_RUSTFLAGS="-Zsanitizer=leak" \
cross +nightly build --target aarch64-unknown-linux-gnu -Z build-std -vv
+ cargo metadata --format-version 1 --filter-platform aarch64-unknown-linux-gnu
Warning: Falling back to `cargo` on the host.
+ cargo +nightly build --target aarch64-unknown-linux-gnu -Z build-std -vv
Compiling compiler_builtins v0.1.73I believe this affects every image. Not every rustflag however affects this: only unstable -Z flags are affected. For example, this works:
$ CARGO_TARGET_AARCH64_UNKNOWN_LINUX_GNU_RUSTFLAGS="-C panic=abort" \
cross +nightly build --target aarch64-unknown-linux-gnu -Z build-std -vvNote that this does not occur when using cross rustc and passing the options: the following works as expected:
$ cross +nightly rustc --target x86_64-unknown-linux-gnu -- -Zself-profile -Zsanitizer=leakWhat target(s) are you cross-compiling for?
aarch64-unknown-linux-gnu
Which operating system is the host (e.g computer cross is on) running?
- macOS
- Windows
- Linux / BSD
- other OS (specify in description)
What architecture is the host?
- x86_64 / AMD64
- arm32
- arm64 (including Mac M1)
What container engine is cross using?
- docker
- podman
- other container engine (specify in description)
cross version
cross 0.2.2 and latest main
Example
No response
Additional information / notes
This affected cross prior to #869 being merged, so this is not related to that.