Can a false timestamp on a makefile break a build?
Today, I tried to run a building script on sources that were in a mounted NAS directory. During the build, I received a warning saying that one of the cmake generated files had a modification time 13 s in the future. Subsequently the build failed, because a header file could not be found. Now, this building script has never given me any troubles before, and the header file was exactly where it was supposed to be, so I was quite puzzled by the error. However, when I inspected the cmake generated file with the false timestamp, it turned out to contain the CCX_INCLUDES. This makes me suspect that the timestamp is in fact the cause of the problem, but I do not understand how it can influence the build. Could someone please shed a light on this?
Make Target Name From Another
How can I build many variants of one project using makefile?
optional flavours of a target
Lighttpd Refernces Wrong Lib Location
Run multiple processes (multiple watch commands)
How to layout Makefiles where target depends on multiple linux builds
Strip all spaces from a variable and append to another variable if not blank
make: Error in ifneq: word unexpected (expecting “)”)
makefile: implicit rules: same target different prerequisites
Why does following makefile rebuilt target “build” everytime
Behaviour of VPATH in makefile
Difference between the ifeq directive and the if function in GNU Make
How could I save the Clang diagnostics into a file?
meaning of “all-before” and “all-after” in makefiles
Rebuilding object files with Makefile
How does gnu Make handle the dependencies?