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 runs all targets
convert to lowercase in a Makefile
Makefile patsubst multiple occcurence in replacement pattern
Check File Existence with Makefile Conditional
Alias target name in Makefile
Makefile pass arguments to a C program
How to modify librtmp Makefile to remove version suffix?
No Rule to make but the rule is there?
Trouble printing newline in makefile
Need an specefic order of the targets in the Makefile
Makefile rule dependencies defined in several lines
equivalent of pipefail in GNU make?
Ranlib not found
Makefile experts needed
How to downgrade zeromq from version 4.0.4 to 3.2.4
why buildroot fails to make the .config?