Follow-up Comment #4, bug #40610 (project make): Yes, it's a tmpfs bug; this has been confirmed. See the downstream url. It would be better if gmake could avoid looping, but if you don't see a way, then I guess it isn't reasonably possible.
Does it re-exec itself after rebuilding all included makefiles, or after each one? If it's after all, it could conceivably add a single option to inhibit regenerating included makefiles; then if one's out of date on the second run it can fail with a cogent error message. Based on the debug output, it looks like this might be the case. But if it restarts itself after every one there's not much hope. In any case, it's not my makefile that triggered it. I know better than to have rules depend on directories. :-) And before I figured out what was really going on I'd already found a workaround that was adequate for that particular package, which is the only one out of 13,000+ that stepped on this problem: I added "false" to the end of its make depend recipe. This causes the loop to terminate but does not fail the overall build. (This does seem like a bug in its own right, even though it's currently convenient.) Given what's going on the smallest and most reliable way to fix it (given that the actual makefile involved is fairly complicated and fairly fragile) is to change the depend rule to do $(MAKE) objdir instead of depending on objdir. This is a localized change, and while it causes a mostly-useless extra make invocation, that doesn't matter much. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?40610> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/ _______________________________________________ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make