Self-Healing CI: Auto-Installing a Missing Compiler / Build Tool

When a native build dies because there is no compiler on the runner, the fix is mechanical: install the toolchain - and bake it in so it never recurs.

The problem

A step that compiles a native extension fails with gcc: command not found, error: command "cc" failed, or a missing C/C++ toolchain. The source is fine; the runner simply lacks a compiler. A human installs the build toolchain and the build passes unchanged.

Typical symptom

error: command 'gcc' failed: No such file or directory
# or
error: linker `cc` not found ... is a compiler installed?

Why it happens

Many packages ship source that must be compiled on install (native Python/Ruby/Node extensions, Rust crates linking C). That step needs a C/C++ compiler and linker, which a minimal runner image does not include by default.

The gap is deterministic - it fails every run until a compiler is present - but it is a mechanical setup gap, not a defect in your code.

The manual fix

The manual fix is to install the toolchain, then make it permanent:

Install a C/C++ build toolchain (e.g. build-essential on Debian/Ubuntu, gcc/make on RHEL-family).
Re-run the step so the native build can compile.
Add the toolchain to your workflow or runner image so future runs already have it.

Manual fix

sudo apt-get update && sudo apt-get install -y build-essential
# RHEL-family: sudo dnf groupinstall -y "Development Tools"

How this gets automated

Because the missing tool is named in the error and the remedy is a well-scoped install from a known-safe set, this can be automated safely. A self-healing CI pipeline installs the missing compiler/toolchain, retries the step, and can propose a durable change to your setup so the gap is closed for good - turning a recurring native-build failure into a one-time, permanent fix.