Cross uses wrong ar when cross compiling ring on M1 Mac

[jwalton]

Checklist

• I've looked through the issues and pull requests for similar reports

Describe your issue

When cross-compiling to musl on M1 mac, cross tries to run musl-ar instead of just ar, but musl-ar isn't in the PATH for the build image.

What target(s) are you cross-compiling for?

i586-unknown-linux-musl

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.5

Example

$ cargo new bug
$ cd bug
$ cargo add ring
$ CROSS_CONTAINER_OPTS="--platform linux/amd64" cross build --release --target x86_64-unknown-linux-musl

--snip--

  error occurred: Command ZERO_AR_DATE="1" "musl-ar" "cq" "/target/x86_64-unknown-linux-musl/release/build/ring-ecebd54999486096/out/libring-core.a" "/target/x86_64-unknown-linux-musl/release/build/ring-ecebd54999486096/out/aesni-x86_64-elf.o" "/target/x86_64-unknown-linux-musl/release/build/ring-ecebd54999486096/out/vpaes-x86_64-elf.o" "/target/x86_64-unknown-linux-musl/release/build/ring-ecebd54999486096/out/x86_64-mont-elf.o" "/target/x86_64-unknown-linux-musl/release/build/ring-ecebd54999486096/out/x86_64-mont5-elf.o" "/target/x86_64-unknown-linux-musl/release/build/ring-ecebd54999486096/out/chacha-x86_64-elf.o" "/target/x86_64-unknown-linux-musl/release/build/ring-ecebd54999486096/out/p256-x86_64-asm-elf.o" "/target/x86_64-unknown-linux-musl/release/build/ring-ecebd54999486096/out/aesni-gcm-x86_64-elf.o" "/target/x86_64-unknown-linux-musl/release/build/ring-ecebd54999486096/out/ghash-x86_64-elf.o" "/target/x86_64-unknown-linux-musl/release/build/ring-ecebd54999486096/out/sha512-x86_64-elf.o" "/target/x86_64-unknown-linux-musl/release/build/ring-ecebd54999486096/out/chacha20_poly1305_x86_64-elf.o" "/target/x86_64-unknown-linux-musl/release/build/ring-ecebd54999486096/out/sha256-x86_64-elf.o" "/target/x86_64-unknown-linux-musl/release/build/ring-ecebd54999486096/out/aes_nohw.o" "/target/x86_64-unknown-linux-musl/release/build/ring-ecebd54999486096/out/montgomery.o" "/target/x86_64-unknown-linux-musl/release/build/ring-ecebd54999486096/out/montgomery_inv.o" "/target/x86_64-unknown-linux-musl/release/build/ring-ecebd54999486096/out/limbs.o" "/target/x86_64-unknown-linux-musl/release/build/ring-ecebd54999486096/out/mem.o" "/target/x86_64-unknown-linux-musl/release/build/ring-ecebd54999486096/out/poly1305.o" "/target/x86_64-unknown-linux-musl/release/build/ring-ecebd54999486096/out/crypto.o" "/target/x86_64-unknown-linux-musl/release/build/ring-ecebd54999486096/out/curve25519.o" "/target/x86_64-unknown-linux-musl/release/build/ring-ecebd54999486096/out/ecp_nistz.o" "/target/x86_64-unknown-linux-musl/release/build/ring-ecebd54999486096/out/ecp_nistz256.o" "/target/x86_64-unknown-linux-musl/release/build/ring-ecebd54999486096/out/gfp_p256.o" "/target/x86_64-unknown-linux-musl/release/build/ring-ecebd54999486096/out/gfp_p384.o" "/target/x86_64-unknown-linux-musl/release/build/ring-ecebd54999486096/out/cpu-intel.o" "/target/x86_64-unknown-linux-musl/release/build/ring-ecebd54999486096/out/poly1305_vec.o" with args "musl-ar" did not execute successfully (status code exit status: 127).

Additional information / notes

No response

[jwalton]

Possibly related to #1100?

[Emilgardis]

ring is using the wrong ar, try setting these env vars

TARGET_AR=i586-linux-musl-ar
TARGET_CC=i586-linux-musl-gcc

so

# Cross.toml
[target.i586-unknown-linux-musl]
env.passthrough = ["TARGET_CC=i586-linux-musl-gcc", "TARGET_AR=i586-linux-musl-ar"]

[jwalton]

This fixed it for me! Thanks!

[Emilgardis]

Awesome! In the newer images we've added these envvars so it should be solved if you use cross from main