[bug #60435] Chained pattern rules with multiple targets not removing all intermediate files

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

[bug #60399] Incorrect dependencies with grouped targets

Follow-up Comment #3, bug #60399 (project make): There is this difference in behavior between the 2 makefiles. In the cause of .PHONY: b a b&:; touch a b b is phony and a is not phony. In the case of .PHONY: force b: force a b&:; touch a b Both a and b depend on force. Do you think make shou

[bug #60399] Incorrect dependencies with grouped targets

Update of bug #60399 (project make): Item Group: Bug => Enhancement ___ Follow-up Comment #2: Re-reading this I think I want to retract my earlier comment that this does not seem right. I thin

[bug #60281] Directory in directory in $PATH shadows binaries in $PATH

Update of bug #60281 (project make): Status:None => Duplicate Open/Closed:Open => Closed ___ Reply to this item at:

[bug #60557] Built-in rule for preprocessing assembler programs doesn't work as documented

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

[bug #60777] Command line switch --trace disables -d.

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

[bug #57778] Stop looking for an included file once found, even if cannot be opened.

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

[bug #60795] Document that .PHONY included makefiles are rebuilt but not reread

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

[bug #60799] Parser chokes on second expansion of a prerequisite with ; o #

Follow-up Comment #4, bug #60799 (project make): But my point is that $$ is NOT (intended to be) special to make. That's why make doesn't do parentheses matching which it sees it. In other words, to make this: bye: $$(hello#world) is treated the same way as this: bye: D(hello#world) for

Re: Parallel job instance identifiers?

Wait, it is a dumb question. Never mind. David On Mon, Sep 6, 2021 at 7:58 AM David Boyce wrote: > > One possibility would be for make to write out bytes with values > 0,1,2,3... then when it gets to 255 start over again ... > > I hope this sin't a dumb question, I've never worked with the job

[bug #60841] misleading statement in the manual

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

Re: Parallel job instance identifiers?

> One possibility would be for make to write out bytes with values 0,1,2,3... then when it gets to 255 start over again ... I hope this sin't a dumb question, I've never worked with the job server, but hy not use the value of the file descriptor from the parent side as the token to send down the p

Re: Parallel job instance identifiers?

Paul Smith wrote: > On Fri, 2021-08-13 at 14:14 +0100, Howard Chu via Bug reports and > discussion for GNU make wrote: >> I'm looking for a way to expose a job ID number to the individual >> jobs, in a consecutive range from 1-[number of jobs]. Not just >> unique numbers, for that we could just use

[bug #61122] Add a .SECONDARY example.

Follow-up Comment #3, bug #61122 (project make): A bit more context about this patch. Recently a person showed me a makefile with an incorrect use of .SECONDARY. When i asked about this, the person explained, that there is no example of when .SECONDARY is useful. _

[bug #60904] More accurate description of intermediate files

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

[bug #61122] Add a .SECONDARY example.

Follow-up Comment #2, bug #61122 (project make): Well, i thought it was obvious that this applies when hello.tsk exists and is up to date in regards to hello.c and bye.c. But apparently, this is not obvious. i applied another patch which explicitly states when this applies. (file #51875)

[bug #61122] Add a .SECONDARY example.

Follow-up Comment #1, bug #61122 (project make): How can make avoid the rebuild? You can't link these two object files into a binary if one or both of them don't exist! ___ Reply to this item at:

[bug #61122] Add a .SECONDARY example.

Additional Item Attachment, bug #61122 (project make): File name: sv_61122_doc_secondary_example.diff Size:1 KB ___ Reply to this item at:

Re: Parallel job instance identifiers?

On Fri, 2021-08-13 at 14:14 +0100, Howard Chu via Bug reports and discussion for GNU make wrote: > I'm looking for a way to expose a job ID number to the individual > jobs, in a consecutive range from 1-[number of jobs]. Not just > unique numbers, for that we could just use $$ already. The purpose

[bug #61122] Add a .SECONDARY example.

URL: Summary: Add a .SECONDARY example. Project: make Submitted by: dgoncharov Submitted on: Mon 06 Sep 2021 02:35:26 PM UTC Severity: 3 - Normal Item Group: Documentati