public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
* [Bug other/103331] New: There should be a rule to make build.log in the top-level Makefile
@ 2021-11-19 13:17 egallager at gcc dot gnu.org
2021-11-20 14:05 ` [Bug other/103331] " egallager at gcc dot gnu.org
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: egallager at gcc dot gnu.org @ 2021-11-19 13:17 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103331
Bug ID: 103331
Summary: There should be a rule to make build.log in the
top-level Makefile
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: build
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: egallager at gcc dot gnu.org
Target Milestone: ---
In the top-level Makefile, there's a target warning.log that depends on a
build.log file, but trying to do `make warning.log` results in:
make: *** No rule to make target `build.log', needed by `warning.log'. Stop.
All files depended on by current Makefile targets should have rules to build
them from the Makefiles themselves, IMO.
^ permalink raw reply [flat|nested] 4+ messages in thread* [Bug other/103331] There should be a rule to make build.log in the top-level Makefile 2021-11-19 13:17 [Bug other/103331] New: There should be a rule to make build.log in the top-level Makefile egallager at gcc dot gnu.org @ 2021-11-20 14:05 ` egallager at gcc dot gnu.org 2023-10-15 19:56 ` egallager at gcc dot gnu.org 2023-10-20 7:22 ` egallager at gcc dot gnu.org 2 siblings, 0 replies; 4+ messages in thread From: egallager at gcc dot gnu.org @ 2021-11-20 14:05 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103331 Eric Gallager <egallager at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |neroden at gcc dot gnu.org --- Comment #1 from Eric Gallager <egallager at gcc dot gnu.org> --- git blame says the dependency has been there since Nathanael Nerode first created Makefile.tpl back in g:95ddd785 in 2002... ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug other/103331] There should be a rule to make build.log in the top-level Makefile 2021-11-19 13:17 [Bug other/103331] New: There should be a rule to make build.log in the top-level Makefile egallager at gcc dot gnu.org 2021-11-20 14:05 ` [Bug other/103331] " egallager at gcc dot gnu.org @ 2023-10-15 19:56 ` egallager at gcc dot gnu.org 2023-10-20 7:22 ` egallager at gcc dot gnu.org 2 siblings, 0 replies; 4+ messages in thread From: egallager at gcc dot gnu.org @ 2023-10-15 19:56 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103331 --- Comment #2 from Eric Gallager <egallager at gcc dot gnu.org> --- 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? ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug other/103331] There should be a rule to make build.log in the top-level Makefile 2021-11-19 13:17 [Bug other/103331] New: There should be a rule to make build.log in the top-level Makefile egallager at gcc dot gnu.org 2021-11-20 14:05 ` [Bug other/103331] " egallager at gcc dot gnu.org 2023-10-15 19:56 ` egallager at gcc dot gnu.org @ 2023-10-20 7:22 ` egallager at gcc dot gnu.org 2 siblings, 0 replies; 4+ messages in thread From: egallager at gcc dot gnu.org @ 2023-10-20 7:22 UTC (permalink / raw) To: gcc-bugs 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... ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2023-10-20 7:22 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2021-11-19 13:17 [Bug other/103331] New: There should be a rule to make build.log in the top-level Makefile egallager at gcc dot gnu.org 2021-11-20 14:05 ` [Bug other/103331] " egallager at gcc dot gnu.org 2023-10-15 19:56 ` egallager at gcc dot gnu.org 2023-10-20 7:22 ` egallager at gcc dot gnu.org
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).