-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Linker error on rustc 1.86.0-nightly (f85c6de55 2025-01-26)
when cross compiling to aarch64-unknown-linux-musl
#136132
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
Comments
@VorpalBlade this output is coming directly from your linker, not from rustc. rustc is just forwarding it. this looks very similar to #136088. i wonder if this is an upstream issue in cross, maybe they need to remove set -x from their linker wrapper. |
yeah this looks like it https://github.com/cross-rs/cross/blob/main/docker/musl-gcc.sh |
Issue filed with them: cross-rs/cross#1618 |
I don't quite get why only aarch64 though. I also cross compile musl to RISCV, ARM32, etc. Hm. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@briansmith I'm fairly sure your issue is a different issue, since you got a linker exit code of 1 and an actual "error:" line. The case was about cargo erroring on the linker outputing on stderr and exiting with code 0. |
This got caught in CI: https://github.com/VorpalBlade/chezmoi_modify_manager/actions/runs/12986156450/job/36212410530?pr=199
I can't actually see where it says the actual linker error or warning though? Also stable works fine. I use cross for building.
I expected to see this happen: Linking should succeed, or if it doesn't, and rustc blames the linker, the actual linker error/warning should be visible
Instead, this happened: Very confusing error message, with no actual error or warning?
Meta
rustc --version --verbose
:Backtrace
The text was updated successfully, but these errors were encountered: