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?
Detecting unused makefile command line arguments
CheckCXXCompilerFlag or CheckCCompilerFlag to check a group of flags at once
c++ how should the makefile look
Makefile generic binaries compilations
getting error with this makefile
How do I concat a system call in a Makefile?
Understanding Makefile Syntax and Variables
grub_script.yy.c:2354:13: error: 'yy_fatal_error' defined but not used
Make target with / at the end?
Problems with GNU Make dynamic rules
generic makefile to create multiple executable using different flags
Chane options in GCC c++ make files
Append compile flags to CFLAGS and CXXFLAGS while configuration/make
saving PID of spawned process within a Makefile
Makefile clean all target is called twice when explicitly invoked
Get make makefile warning output to include print newlines