I think it makes sense to mention MAKE_RESTARTS in the section on
remaking makefiles.
Thanks,
Florian
>From 4ded2321ab3ec09d8cc8a648e8de53d53a9756d3 Mon Sep 17 00:00:00 2001
From: Florian Weimer <fwei...@redhat.com>
Date: Tue, 24 Oct 2017 11:26:29 +0200
Subject: [PATCH] * make.texi (Remaking Makefiles): Mention MAKE_RESTARTS
---
doc/make.texi | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/doc/make.texi b/doc/make.texi
index 8810f2b..18fc10d 100644
--- a/doc/make.texi
+++ b/doc/make.texi
@@ -1322,7 +1322,12 @@ all makefiles have been checked, if any have actually been changed,
@code{make} starts with a clean slate and reads all the makefiles over
again. (It will also attempt to update each of them over again, but
normally this will not change them again, since they are already up to
-date.)@refill
+date.) Each time processing is restarted in this way, @code{make} will
+increment the value of the @code{MAKE_RESTARTS} variable (starting with
+@code{1} at the first restart; the variable is unset before that). You
+can use @code{MAKE_RESTARTS} with a conditional section
+(@pxref{Conditionals, ,Conditional Parts of Makefiles}) to avoid
+infinite recursion.
If you know that one or more of your makefiles cannot be remade and
you want to keep @code{make} from performing an implicit rule search
--
2.13.6
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make
