On Thu, 2017-06-22 at 15:56 +0200, SF Markus Elfring wrote: > > As always, if you can't figure out what's going on running "make > > -d" will help you more than we can. > > I wonder about the information “Re-executing[1]: make --no-builtin- > rules -d” there. > Unfortunately, I do not recognise so far which rule triggers this > action.
This is exactly the situation I suggested as the second reason why you might be seeing the output twice: https://www.gnu.org/software/make/manual/html_node/Remaking-Makefiles.html If the makefile, or any of the files it includes, is updated by make then make will re-execute itself and re-read all the makefiles from scratch so it can see the updated content. When that happens, obviously all the $(info ...) functions etc. will be re-expanded. > I imagine that my extra information display might be useful. > Should I check anyhow then if the included dependency file was > modified? > > Or is it more desirable to deactivate the message “modules without > mli files”? That's up to you; we can't decide for you. If you decide you want to test whether or not this makefile is being read due to the initial parse versus a re-execution of make you can check the MAKE_RESTARTS variable: https://www.gnu.org/software/make/manual/html_node/Special-Variables.html Or you can just remove these $(info ...) statements. _______________________________________________ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make
