Skip to content
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

Cross running tests fails due to missing C compiler #98837

Closed
JakobDegen opened this issue Jul 3, 2022 · 3 comments
Closed

Cross running tests fails due to missing C compiler #98837

JakobDegen opened this issue Jul 3, 2022 · 3 comments
Labels
A-testsuite Area: The testsuite used to check the correctness of rustc

Comments

@JakobDegen
Copy link
Contributor

Beginning with #97513 (cc @jyn514 ) , RUST_BACKTRACE=1 x test src/test/mir-opt/ --target i686-unknown-linux-gnu fails on my system, printing:

Building rustbuild
    Finished dev [unoptimized] target(s) in 0.03s
thread 'main' panicked at '

couldn't find required command: "i686-linux-gnu-gcc"

', sanity.rs:59:13
stack backtrace:
   0: rust_begin_unwind
             at /rustc/daf68b1f766e67ffe040260b15c218301853386a/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
             at /rustc/daf68b1f766e67ffe040260b15c218301853386a/library/core/src/panicking.rs:142:14
   2: bootstrap::sanity::Finder::must_have::{{closure}}
             at ./src/bootstrap/sanity.rs:59:13
   3: core::option::Option<T>::unwrap_or_else
             at /rustc/daf68b1f766e67ffe040260b15c218301853386a/library/core/src/option.rs:805:21
   4: bootstrap::sanity::Finder::must_have
             at ./src/bootstrap/sanity.rs:58:9
   5: bootstrap::sanity::check
             at ./src/bootstrap/sanity.rs:159:13
   6: bootstrap::Build::new
             at ./src/bootstrap/lib.rs:522:13
   7: bootstrap::main
             at ./src/bootstrap/bin/main.rs:34:5
   8: core::ops::function::FnOnce::call_once
             at /rustc/daf68b1f766e67ffe040260b15c218301853386a/library/core/src/ops/function.rs:248:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Build completed unsuccessfully in 0:00:00

I'm not sure if this is intentional - the PR mentions that there is a vendoring change, so that might be related. It would be nice if this worked though.

@JakobDegen
Copy link
Contributor Author

@rustbot label A-testsuite

@rustbot rustbot added the A-testsuite Area: The testsuite used to check the correctness of rustc label Jul 3, 2022
@JakobDegen
Copy link
Contributor Author

Wait, hold on, I just started reading this right. Why does it think that i686-linux-gnu-gcc is the name of a C compiler? That's not typical, is it?

@JakobDegen
Copy link
Contributor Author

Investigated a little bit more. The cause of this issue is the version bump of cc. Setting CC=clang fixes the issue. I think this might be a bug on their end, but at least going to close this for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-testsuite Area: The testsuite used to check the correctness of rustc
Projects
None yet
Development

No branches or pull requests

2 participants