Verify build prerequisites before relying on an existing Makefile
For custom-runtime build targets, do not assume the checked-in Makefile is sufficient. Check the actual prerequisites before compiling.
Procedure:
- Verify the required toolchain is actually present:
If the cross compiler is missing, install it first, e.g.:which mips-linux-gnu-gcc mipsel-linux-gnu-gcc clang gcc nodeapt-get update && apt-get install -y gcc-mips-linux-gnu - Verify task-provided custom headers exist:
A source file that includes a missing header cannot build until that header is provided.find / -name 'my_stdlib.h' 2>/dev/null - Check what the existing Makefile actually produces and link against:
Compare that with the runtime's expected artifact name and architecture. For example, a host Makefile producinggrep -nE '^(TARGET|OUTPUT|.*-o )|(-lX11|doomgeneric)' Makefiledoomgenericwith-lX11will not satisfy a VM that callsrunElf("doomgeneric_mips"). - Build explicitly for the requested target and output filename, or patch the Makefile so the target, compiler, and artifact name all match the runtime expectation.
Why: in this run none of the normal build assumptions held; using the repository's host Makefile would not have produced the requested artifact.
Supporting evidence: make-doom-for-mips (this batch).