[bug #66050] add option --shuffle=nosort

Follow-up Comment #1, bug #66050 (group make): I'm sorry but I don't understand this issue. Can you clarify? I don't know what the --shuffle option has to do with sorting: shuffled prerequisites are never sorted (that would go against the entire concept). Are you suggesting a way to always buil

[bug #65999] make --debug=makefile could be more descriptive

Follow-up Comment #1, bug #65999 (group make): Whether or not you specify "makefile" is not relevant for this issue; these messages are printed while building the normal targets. In fact they're printed even with "basic" debug level. However they can be made more clear I agree. ___

[bug #65999] make -d could be more descriptive WRT phony targets

Update of bug #65999 (group make): Summary: make --debug=makefile could be more descriptive => make -d could be more descriptive WRT phony targets ___ Reply to this item at: _

[bug #66030] --trace only shows the "primary" ($@) target

Follow-up Comment #3, bug #66030 (group make): I think we are just disagreeing over a matter of technical semantics. Make is showing the target it is currently considering, and which it determined to be out of date and so forced make to run the recipe. In your example, that target is "foo.h". T

[bug #66030] --trace only shows the "primary" ($@) target

Follow-up Comment #4, bug #66030 (group make): I'm not trying to be argumentative, really, but I still feel like we're not quite coming to closure on the same topic so let me try one more time. It seems to me there's a significant difference between these two rules: foo.h foo.c: ; foo.%: ; rec

[bug #66050] add option --shuffle=nosort

Follow-up Comment #2, bug #66050 (group make): > Are you suggesting a way to always build prerequisites > in an order sorted by their name? The opposite: build *WILDCARD* prerequisites in an order *NOT* sorted by their name. $ touch {a..z} # Current: $ make -E "all: *; @echo $^" a b c d e f g

[bug #66030] --trace only shows the "primary" ($@) target

Follow-up Comment #5, bug #66030 (group make): You are talking about what make knows and what, of the things it knows, it should print in this situation. I don't disagree with any of that. I'm talking about what make _actually does today_. There can be no disagreement about that, since it does

[bug #65917] --dry-run doesn't handle pattern rules with multiple targets correctly

Update of bug #65917 (group make): Status:None => Fixed Assigned to:None => psmith Open/Closed:Open => Closed Fixed Release:

[bug #65982] make --trace does not explain remade include files

Update of bug #65982 (group make): Status:None => Fixed Assigned to:None => psmith Open/Closed:Open => Closed Operating System:

[bug #65999] make -d could be more descriptive WRT phony targets

Update of bug #65999 (group make): Status:None => Fixed Assigned to:None => psmith Open/Closed:Open => Closed Operating System:

[bug #66018] Recommendation: document .ONESHELL behavior in sections concerning line prefixes [@+-]

Update of bug #66018 (group make): Status:None => Fixed Assigned to:None => psmith Open/Closed:Open => Closed Fixed Release:

[bug #66037] An infinite loop with MAKEFLAGS on the command line.

Update of bug #66037 (group make): Status:None => Fixed Open/Closed:Open => Closed Operating System:None => Any Fixed Release:

[bug #66030] --trace only shows the "primary" ($@) target

Update of bug #66030 (group make): Status:None => Fixed Assigned to:None => psmith Open/Closed:Open => Closed Operating System:

[bug #65739] Add warnings circular-dep and circular-extra-dep.

Update of bug #65739 (group make): Status:None => Fixed Open/Closed:Open => Closed Fixed Release:None => SCM __

[bug #66050] add option --shuffle=nosort

Follow-up Comment #3, bug #66050 (group make): I am not a fan having the --shuffle argument modify the behavior of $(wildcard ...) as they are completely disjoint facilities that have nothing to do with each other. IMO it will be confusing. The result of wildcard has swung back and forth between