[bug #59169] Add a --debug=why category for the -d/--debug option

2020-12-06 Thread David Boyce
Follow-up Comment #5, bug #59169 (project make): I'd consider this change too small to require attribution so not to worry! ___ Reply to this item at:

[bug #59169] Add a --debug=why category for the -d/--debug option

2020-12-06 Thread Paul D. Smith
Update of bug #59169 (project make): Status:None => Fixed Assigned to:None => psmith Open/Closed:Open => Closed Operating System:

[bug #59169] Add a --debug=why category for the -d/--debug option

2020-09-28 Thread David Boyce
Follow-up Comment #3, bug #59169 (project make): I've updated the patch a bit to coalesce message style. The current --trace output comes in one of two formats: Makefile:12: target 'foobar' does not exist Makefile:15: update target 'hello.o' due to: hello.c According to whether there's a valid

[bug #59169] Add a --debug=why category for the -d/--debug option

2020-09-26 Thread David Boyce
Follow-up Comment #2, bug #59169 (project make): I've posted a patch to do this. Very lightly tested but after all it doesn't add or change any functionality. ___ Reply to this item at:

[bug #59169] Add a --debug=why category for the -d/--debug option

2020-09-26 Thread David Boyce
Additional Item Attachment, bug #59169 (project make): File name: debug_print_why.patch Size:2 KB ___ Reply to this item at:

[bug #59169] Add a --debug=why category for the -d/--debug option

2020-09-26 Thread Paul D. Smith
Follow-up Comment #1, bug #59169 (project make): I don't fully remember why I created --trace as a separate option. I think the idea was that it would be useful for "normal users" who weren't trying to debug makefiles, but rather were trying to trace their build operations, so putting it under

[bug #59169] Add a --debug=why category for the -d/--debug option

2020-09-22 Thread David Boyce
URL: Summary: Add a --debug=why category for the -d/--debug option Project: make Submitted by: boyski Submitted on: Wed 23 Sep 2020 02:22:35 AM UTC Severity: 3 - Normal