[bug #22923] option to prevent "interspersed" output in parallel builds

Follow-up Comment #5, bug #22923 (project make): Another idea mentioned in a Python bug discussion on file handles contention is to have each spawned make process redirect stdout and stderr of its spawned actions to a socket opened by the main make process. (Perhaps, each make process could do t

[bug #22923] option to prevent "interspersed" output in parallel builds

Follow-up Comment #9, bug #22923 (project make): I agree with comment #2 that polling pipes would incur unnecessary overhead and that the generic solution would pair each spawned action against the pre-defined template of a "logger" command. Looking at the recipient of messages in the existing i

[bug #28983] forcing a target matching a pattern rule shadows the rule's actions

URL: Summary: forcing a target matching a pattern rule shadows the rule's actions Project: make Submitted by: ilgiz Submitted on: Mon 22 Feb 2010 03:35:05 PM EST Severity: 3 - Normal

[bug #28983] forcing a target matching a pattern rule shadows the rule's actions

Additional Item Attachment, bug #28983 (project make): File name: force-build-of-a-target-matching-a-pattern-rule.mak Size:0 KB ___ Reply to this item at: _

[bug #28983] forcing a target matching a pattern rule shadows the rule's actions

Follow-up Comment #1, bug #28983 (project make): The work-around, as I see it in one build system, is to add an extra dummy target, = ALWAYS-BUILD: ; file.o: ALWAYS-BUILD = Same with the explicit noisy target, ===

[bug #28983] forcing a target matching a pattern rule shadows the rule's actions

Follow-up Comment #2, bug #28983 (project make): Correction: the semicolon at the end of the work-around lines should be removed because it assigned an empty set of actions to the artificial target. GNU make will complain if another rule assigns any actions to the same target, .PHONY: foo.o ;

[bug #28983] forcing a target matching a pattern rule shadows the rule's actions

Follow-up Comment #4, bug #28983 (project make): The GNU make manual both supports and defeats Matt's statement. "A phony target is one that is not really the name of a file." [..] "Once this is done, `make clean' will run the commands regardless of whether there is a file named clean."

[bug #28983] forcing a target matching a pattern rule shadows the rule's actions

Follow-up Comment #6, bug #28983 (project make): The following tests show that .PHONY's pre-requisites are normally rebuilt regardless of existence of a file with the same name. This works, $ cat test-force.mak default: file.o .PHONY: file.o file.o: echo Building $...@... > $@ $

[bug #28983] forcing a target matching a pattern rule shadows the rule's actions

Follow-up Comment #7, bug #28983 (project make): The following tests show that .PHONY's pre-requisites are normally rebuilt regardless of existence of a file with the same name. This works, $ cat test-force.mak default: file.o .PHONY: file.o file.o: echo Building $...@... > $@ $