On Wed, Aug 12, 2026 at 5:49 AM Eric Gallager <[email protected]> wrote: > > On Mon, Aug 10, 2026 at 5:39 PM Uros Bizjak <[email protected]> wrote: > > > > mail-report.log has no prerequisites, so once it exists Make > > considers it up to date on every subsequent invocation and the > > recipe never reruns; regenerating it after a fresh test run > > currently requires manually removing the file first. > > > > mail-report-with-warnings.log has the same problem despite > > depending on warning.log: it always needs to regenerate on > > demand rather than only when its prerequisite changes. > > > > Mark both as .PHONY so they rerun on every invocation, matching > > their actual use as on-demand report generators rather than > > cacheable build artifacts. warning.log itself is left alone, as > > its dependency on build.log is tracked correctly and should keep > > using normal timestamp-based rebuilding. > > > > How are you supposed to make build.log, anyways? I was trying to > figure it out in issue 103331, but I couldn't figure it out: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103331
make -j 4 2>&1 | tee build.log Uros.
