Module sanity 

Sanity checking and tool selection performed by bootstrap.

This module ensures that the build environment is correctly set up before executing any build tasks. It verifies required programs exist (like git and cmake when needed), selects some tools based on the environment (like the Python interpreter), and validates that C compilers for cross-compiling are available.

In theory if we get past this phase it’s a bug if a build fails, but in practice that’s likely not true!

Re-exports

use std::collections::HashMap; 🔒

use std::collections::HashSet; 🔒

use std::ffi::OsStr; 🔒

use std::ffi::OsString; 🔒

use std::path::PathBuf; 🔒

use std::env; 🔒

use std::env; 🔒

use std::fs; 🔒

use crate::core::build_steps::tool; 🔒

use crate::core::builder::Builder; 🔒

use crate::core::config::flags::Subcommand; 🔒

use crate::core::config::CompilerBuiltins; 🔒

use crate::core::config::DebuggerPath; 🔒

use crate::core::config::Target; 🔒

use crate::core::session::Session; 🔒

use crate::utils::exec::command; 🔒

use crate::utils::helpers; 🔒

use crate::utils::helpers::t; 🔒

Structs

Finder

Constants

LIBSTDCXX_MIN_VERSION_THRESHOLD 🔒

Minimum version threshold for libstdc++ required when using prebuilt LLVM from CI (withllvm.download-ci-llvm option).

STAGE0_MISSING_TARGETS 🔒

During sanity checks, we search for target tuples to determine if they exist in the compiler’s built-in target list (rustc --print target-list). While a target tuple may be present in the in-tree compiler, the stage 0 compiler might not yet know about it (assuming not operating with local-rebuild). In such cases, we handle the targets missing from stage 0 in this list.

Functions

check 🔒