Cross.toml

# RC-9 (v1.0.98): the committed `.cargo/config.toml` forces
# `[target.x86_64-unknown-linux-gnu] linker = "clang"` + `-fuse-ld=mold`, which
# the project volume mounts into the cross container. Inside the container the
# HOST build scripts (`proc-macro2`/`quote`/`libc`) compile for x86_64 and tried
# to link with clang, which is absent from the image — the build died with
# `error: linker 'clang' not found`, failing the `aarch64-unknown-linux-gnu`
# release target and (via `needs: build-matrix`) skipping the GitHub Release.
#
# The previous fix installed clang+mold through an apt `pre-build`, but that step
# also pulled a per-arch native TLS C library that fails to resolve on the cross
# image's apt state and aborts the whole pre-build before clang lands. Instead,
# override the HOST linker back to the default `cc` (always present in the cross
# image) with no mold flag, and pass those env vars through into the container.
# The aarch64 target keeps cross's bundled `aarch64-linux-gnu-gcc`. The crate
# uses reqwest with rustls (ring) only — no native TLS C dependency at all.
[build.env]
passthrough = [
  "CARGO_TARGET_X86_64_UNKNOWN_LINUX_GNU_LINKER",
  "CARGO_TARGET_X86_64_UNKNOWN_LINUX_GNU_RUSTFLAGS",
]