Re: [bug #55137] $(file …) is executed too early when used in recipe

On Mon, 2018-12-03 at 13:36 +0100, Marcin Kasperski wrote: > > > I tried using the following snippet: > > > > > > OUTPUT/something : > > > mkdir -p OUTPUT > > > $(file > $@, something) > > > (…) > > > > That's the defined behaviour. > > All variables are evaluated and all

[bug #55532] Missing prerequisites are not included in $? if .SECONDARY is present

Follow-up Comment #4, bug #55532 (project make): > It's extremely difficult to understand your bug report > because you keep talking about $^ but after a lot of > confused reading of your report and a close look at your > example it's obvious you really mean $? everywhere you write $^. Sorry abou

[bug #52697] Don't start parallel jobs if memory is low

Update of bug #52697 (project make): Summary: More varieties to -j switch => Don't start parallel jobs if memory is low ___ Reply to this item at: ___

[bug #56025] .RECIPEPREFIX doesn't parse line continuations inside function calls

Follow-up Comment #3, bug #56025 (project make): Making the prefix visible is a good idea. I think that it is more compelling if *every* line is prefixed. It creates a good contrast between recipe lines and multi-line variable definitions. Having to leave off a prefix or two is not to bad. I d

[bug #55137] $(file …) is executed too early when used in recipe

Update of bug #55137 (project make): Status:None => Not A Bug Open/Closed:Open => Closed ___ Follow-up Comment #1: It's always been the c

[bug #55088] out-of-bounds read at arscan.c::720

Update of bug #55088 (project make): Status:None => Duplicate Open/Closed:Open => Closed ___ Follow-up Comment #1: A number of updates fo

[bug #55719] Variables containing hyphens are not exported

Update of bug #55719 (project make): Status:None => Not A Bug Open/Closed:Open => Closed ___ Follow-up Comment #1: The variable "foo-bar"

[bug #55720] Make cannot execute shell-builtin commands in recipe

Update of bug #55720 (project make): Item Group:None => Enhancement Status:None => Fixed Assigned to:None => psmith Open/Closed:

[bug #55863] '-load' directive adds its object to the target list if unsuccessful

Follow-up Comment #2, bug #55863 (project make): Can you explain what you mean by "the target list"? I don't know what that means. Can you provide a repro case? ___ Reply to this item at: ___

[bug #55532] Missing prerequisites are not included in $? if .SECONDARY is present

Update of bug #55532 (project make): Status: Not A Bug => None Open/Closed: Closed => Open ___ Reply to this item at:

[bug #55532] Missing prerequisites are not included in $? if .SECONDARY is present

Update of bug #55532 (project make): Status:None => Not A Bug Open/Closed:Open => Closed ___ Follow-up Comment #3: The issue here is that

[bug #55560] .SECONDEXPANSION and eval in target-specific prerequisite lists

Update of bug #55560 (project make): Status:None => Not A Bug Open/Closed:Open => Closed ___ Follow-up Comment #4: I'm afraid I can't rea

Re: "make -jN" requires mechanical changes to a Makefile

> Howard Chu wrote: > > >> Example with one rule creating 4 files: > > >> > > >> all : copy1 > > >> > > >> copy1: Makefile > > >> install -c -m 644 Makefile copy1 > > >> install -c -m 644 Makefile copy2 > > >> install -c -m 644 Makefile copy3 > > >> install -c -m 644

[bug #55532] Missing prerequisites are not included in $? if .SECONDARY is present

Update of bug #55532 (project make): Summary: Missing prerequisites are not included in $^ if .SECONDARY is present => Missing prerequisites are not included in $? if .SECONDARY is present ___ Follow-up Comment #2: It's ex

[bug #55691] New make release plan

Update of bug #55691 (project make): Status:None => Not A Bug Open/Closed:Open => Closed ___ Follow-up Comment #1: Please discuss things