https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103331
--- Comment #3 from Eric Gallager <egallager at gcc dot gnu.org> --- (In reply to Eric Gallager from comment #2) > I'm assuming that the way that build.log is normally generated is by just > appending `| tee build.log` to the end of a normal `make` command? hm, doing it that way results in an empty `warning.log` when doing `make warning.log` to extract the warnings from `build.log`, even when warnings are printed during the actual build output; maybe I need to throw a `2>&1` in there...
