mirror of
https://github.com/Druthulu/BFM-decomp
synced 2026-10-06 09:06:04 -04:00
698 B
698 B
§323a — R53, TWICE IN ONE HOUR: A FAILED BUILD LEAVES THE PREVIOUS BINARY, AND sha1sum READS GREEN (P31 S67)
make build BINARY=ov_SC02_000 returned rc=2 and sha1sum build/ov_SC02_000/ov_SC02_000 printed
the LOCKED hash both times — because the failing object was deleted and the previous link survived.
Trusting the output file over the exit code would have certified a resegmentation that does not
compile as byte-neutral, and scaled it to 38 subsegs. Read the exit code; then read the errors, and
filter warnings out first — gcc-2.7.2's hard errors carry no error: prefix and the one line that
killed cc1 sits mid-stream (the tail of the log was pure warnings in both cases).