From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 7A7EB3858D1E; Fri, 20 Oct 2023 07:22:58 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7A7EB3858D1E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1697786578; bh=kf632JuJ+oQrnaNkGbhFvMP+D/2ElVBqwvOVlMf1Zhk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=hgzGY0csb6Kpn6SzERpyCuGbcdVrFhA4TcAAEAk/n2mNOnASXVLFO1LzVZZ+dFtku tYRvNBbcqLuukvoz3LbEw0Pa13yoXzksHzHO3o7TM/IAyy8awdrR7euY9Pkj5phHj6 B2JKhIE4HlHyp0sbFZSBgONjoJ7sT0I901GmEYnY= From: "egallager at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug other/103331] There should be a rule to make build.log in the top-level Makefile Date: Fri, 20 Oct 2023 07:22:58 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: other X-Bugzilla-Version: 12.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: normal X-Bugzilla-Who: egallager at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D103331 --- Comment #3 from Eric Gallager --- (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 a= re printed during the actual build output; maybe I need to throw a `2>&1` in there...=