I will reconsider usage of .SECONDARY in my applications and that should
work.
Hope this thread highlighted a case worth considering for make devs.
Thanks,
Mikhail
On 05.10.2022 10:51, Dmitry Goncharov wrote:
On Tuesday, October 4, 2022, Mikhail Pomaznoy wrote:
Martin's snippet
On Tuesday, October 4, 2022, Mikhail Pomaznoy wrote:
> Martin's snippet indeed recapitulates the behavior resulted in my initial
> report.
>
> As for Dmitry's reply: I don't understand if *make* does what's expected
> or not.
>
>
> Works as documented. Even though I am not sure this particular
Martin's snippet indeed recapitulates the behavior resulted in my
initial report.
As for Dmitry's reply: I don't understand if /make/ does what's expected
or not. I believed that A.4 being a prereq of A.4.ind will always
trigger the latter being rebuilt if A.4 is newer.
As a side note: I
On Tue, Oct 4, 2022 at 10:08 PM Martin Dorey
wrote:
> Isn't this slightly simplified example sufficient to demonstrate the same
> behavior...
A.4 is a preqreq to T.1 and also a prereq to A.4.ind.
A.4.ind is present and that's why make skips building secondary A.4
and keeps A.4.ind intact,
nt: Tuesday, October 4, 2022 17:16
To: bug-make@gnu.org
Subject: Re: .SECONDARY unexpectedly affects rule invocation
* EXTERNAL EMAIL *
A further note: it's version 4.3 of make
On 10/4/22 14:57, Mikhail Pomaznoy wrote:
Greetings,
I have encountered weird behavior in make and tried to iso
A further note: it's version 4.3 of make
On 10/4/22 14:57, Mikhail Pomaznoy wrote:
Greetings,
I have encountered weird behavior in make and tried to isolate it.
The software was built from source.
I have the following Makefile:
|RECIPE = echo "Making $@ from $^" > $@||
||T.1 : A.4
Greetings,
I have encountered weird behavior in make and tried to isolate it. The
software was built from source.
I have the following Makefile:
|RECIPE = echo "Making $@ from $^" > $@||
||T.1 : A.4 A.4.ind; $(RECIPE)||
||A.4 : A.3 A.3.ind ||
|| $(RECIPE)||
||A.2 :||
|| $(RECIPE)||
