fix for issue 132802: x86 code in wasm32-unknown-unknown binaries by JayAndJef · Pull Request #137457 · rust-lang/rust (original) (raw)

The dist-various-1 job has failed with this PR. You can see the failure here.

2025-03-13T09:44:03.1078299Z [TIMING] core::build_steps::test::Compiletest { compiler: Compiler { stage: 2, host: x86_64-unknown-linux-gnu, forced_compiler: false }, target: thumbv7em-none-eabihf, mode: "run-make", suite: "run-make", path: "tests/run-make", compare_mode: None } -- 91.046
2025-03-13T09:44:03.1080605Z [TIMING] core::build_steps::test::RunMake { compiler: Compiler { stage: 2, host: x86_64-unknown-linux-gnu, forced_compiler: false }, target: thumbv7em-none-eabihf } -- 0.000
2025-03-13T09:44:03.1134493Z Build completed successfully in 0:53:14
2025-03-13T09:44:03.1225863Z + python3 ../x.py dist --host= --target wasm32-unknown-emscripten,arm-unknown-linux-musleabi,arm-unknown-linux-musleabihf,armv5te-unknown-linux-gnueabi,armv5te-unknown-linux-musleabi,armv7-unknown-linux-musleabihf,aarch64-unknown-none,aarch64-unknown-none-softfloat,sparc64-unknown-linux-gnu,x86_64-unknown-redox,thumbv6m-none-eabi,thumbv7m-none-eabi,thumbv7em-none-eabi,thumbv7em-none-eabihf,thumbv8m.base-none-eabi,thumbv8m.main-none-eabi,thumbv8m.main-none-eabihf,riscv32i-unknown-none-elf,riscv32im-unknown-none-elf,riscv32imc-unknown-none-elf,riscv32imac-unknown-none-elf,riscv32imafc-unknown-none-elf,riscv64imac-unknown-none-elf,riscv64gc-unknown-none-elf,armebv7r-none-eabi,armebv7r-none-eabihf,armv7r-none-eabi,armv7r-none-eabihf,thumbv7neon-unknown-linux-gnueabihf,armv7a-none-eabi,aarch64-pc-windows-gnullvm,i686-pc-windows-gnullvm,x86_64-pc-windows-gnullvm
2025-03-13T09:44:03.1769182Z ##[group]Building bootstrap
2025-03-13T09:44:03.2908262Z     Finished `dev` profile [unoptimized] target(s) in 0.11s
2025-03-13T09:44:03.2986926Z ##[endgroup]
2025-03-13T09:44:03.4044673Z cargo:warning=Compiler family detection failed due to error: ToolNotFound: Failed to find tool. Is `sparc64-linux-gnu-g++` installed?
2025-03-13T09:44:03.4050342Z cargo:warning=Compiler family detection failed due to error: ToolNotFound: Failed to find tool. Is `sparc64-linux-gnu-g++` installed?
2025-03-13T09:44:04.3085304Z cargo:warning=Compiler family detection failed due to error: ToolNotFound: Failed to find tool. Is `arm-linux-musleabi-g++` installed?
2025-03-13T09:44:04.3092256Z cargo:warning=Compiler family detection failed due to error: ToolNotFound: Failed to find tool. Is `arm-linux-musleabi-g++` installed?
2025-03-13T09:44:04.6082582Z cargo:warning=Compiler family detection failed due to error: ToolNotFound: Failed to find tool. Is `arm-linux-musleabihf-g++` installed?
2025-03-13T09:44:04.6088903Z cargo:warning=Compiler family detection failed due to error: ToolNotFound: Failed to find tool. Is `arm-linux-musleabihf-g++` installed?
2025-03-13T09:44:04.7963599Z cargo:warning=Compiler family detection failed due to error: ToolNotFound: Failed to find tool. Is `emcc` installed?
2025-03-13T09:44:04.7973991Z cargo:warning=Compiler family detection failed due to error: ToolNotFound: Failed to find tool. Is `em++` installed?
2025-03-13T09:44:04.7984445Z cargo:warning=Compiler family detection failed due to error: ToolNotFound: Failed to find tool. Is `em++` installed?
2025-03-13T09:44:04.9649878Z cargo:warning=Compiler family detection failed due to error: ToolNotFound: Failed to find tool. Is `arm-linux-musleabihf-g++` installed?
2025-03-13T09:44:04.9656382Z cargo:warning=Compiler family detection failed due to error: ToolNotFound: Failed to find tool. Is `arm-linux-musleabihf-g++` installed?
2025-03-13T09:44:04.9805961Z 
2025-03-13T09:44:04.9806671Z thread 'main' panicked at src/bootstrap/src/core/sanity.rs:321:17:
2025-03-13T09:44:04.9807249Z only clang supports building c code for wasm targets
2025-03-13T09:44:04.9807754Z note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Probably we also use GCC for building wasm targets on dist-various-1?