-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Clippy and Miri don't build on arm* and aarch64 dist builders #57812
Comments
The |
Looking at the Cargo invocation Have checked Rust dist code and I'm leaning towards caching or Cargo issue, |
It does not match the target:
|
I haven't worded it properly but it's what I tried to say.
|
I don't believe that's in error, it's how cross compilation works that not everything is compiled for the target. Things like procedural macros and their dependencies are compiled for the host, and in this case something for the host depends on the Something in the build system is setting |
Thanks for the feedback, I thought it should produce tools that will run on the target at this point (it's stage 2 on the dist builder). In this case I'll see if I can figure out where |
Do not set CC, CFLAGS, CXX, CXXFLAGS, AR, RANLIB in bootstrap, it breaks cross compilation Fixes #57812 I tested it in AArch64 Ubuntu container with several days old tree to have all the tools buildable. I did **not** test native builds (amd64 -> amd64), leaving it to CI. r? @alexcrichton
Originally reported as rust-lang/rust-clippy#3682
Full build logs are available here:
armv7 Travis: https://api.travis-ci.com/v3/job/171742865/log.txt
aarch64 Travis: https://api.travis-ci.com/v3/job/171742861/log.txt
These cross toolchains don't accept
-m64
argument which shouldn't be passed for them.I believe the issue is
TARGET
is the same asHOST
("x86_64-unknown-linux-gnu") while it should be arm* or aarch64 depending on the builder.cc @alexcrichton
The text was updated successfully, but these errors were encountered: