Yes, thank you. It looks like with the 1st execution not only included files 
are re-made and a 2nd execution started but also (still in the 1st execution) 
other targets (targets which are not included) also re-made by recipes now 
outdated.

Is this how 'make' works?

Thought that one execution only updates included files and once the whole 
'makefile' is 'stable' will 'make' start working on non-included targets.

(Need to check what brings 'make' to re-make not included targets such early -- 
in the 1st execution. But so far I don't see that what.)

I believe this should be doable without recursive 'make' or '.PHONY' targets.

On Thursday, June 19th, 2025 at 9:05 PM, Paul Smith <psm...@gnu.org> wrote:

> On Thu, 2025-06-19 at 18:12 +0000, WaitronCharm via Bug reports and
> discussion for GNU make wrote:
> 
> > Story is the following. There is a 'makefile' which includes a couple
> > of others, some are itself generated by the same 'make' run (i.e. NO
> > recursive 'make' processes). Issue is that the 'make' re-run is not
> > triggered as ... I wished.
> 
> 
> I'm not sure I understood exactly everything about your post but the
> rules for how things are remade are pretty simple and GNU Make has
> always worked like this:
> 
> First all makefiles are parsed. Then all makefiles are checked for out
> of date-ness and all of them that are out of date, are rebuilt. Then
> if any makefiles were updated, make re-execs itself and starts over.
> 
> --
> Paul D. Smith psm...@gnu.org Find some GNU Make tips at:
> 
> https://www.gnu.org http://make.mad-scientist.net
> "Please remain calm...I may be mad, but I am a professional." --Mad
> Scientist

Reply via email to