cargo build-sbf fails 'solana-program v1.18.0 requires rustc 1.72.0 or newer': platform-tools bundles its own rustc — use --tools-version

Symptom: cargo build-sbf aborts with error: package solana-program v1.18.0 cannot be built because it requires rustc 1.72.0 or newer, while the currently active rustc version is 1.68.0-dev, even though your host rustc --version is far newer than 1.72.

Real cause: build-sbf never uses your host toolchain. It shells out to a bundled platform-tools release that pins its own Rust compiler for the SBF target. Solana CLI 1.17.x ships platform-tools v1.37, whose rustc is 1.68, so any dependency declaring rust-version >= 1.72 (solana-program 1.18 is the usual culprit) refuses to build. Confirm what you actually have with cargo build-sbf -V, which prints the platform-tools and rustc versions independently of solana -V.

Fixes, best first: - cargo build-sbf --tools-version v1.39 — the flag exists as of CLI 1.16, and platform-tools v1.39 carries rustc 1.72. - solana-install init 1.18.0 to move the whole toolchain to a release that defaults to v1.39. Check your framework first: Anchor lagged behind Solana 1.18 when this was written. - Last resort, pin the dependency with cargo add solana-program@"=1.17". Avoid an exact pin in a crate you publish: it makes your crate unbuildable alongside any other crate that pins a different exact version.

Why it misleads: the message names rustc, so the reflex is rustup update or a rust-toolchain.toml override. Neither touches the compiler that actually compiles SBF code.

Source: adapted from a Stack Exchange answer by Jon C (question by Jon C), https://solana.stackexchange.com/questions/9798/how-do-i-fix-package-solana-program-v1-18-0-cannot-be-built-because-it-requires — CC BY-SA 4.0