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?
Pass file argument through to child make
Build issue after the upgradation of clearcase from 126.96.36.199 to 188.8.131.52
Using make file to create package inside nodejs monorepo
How to create targets into specific directory with make?
Compiling superopt on windows
Copying/Accessing files in Build Directory of Autotools
Adding multiple header file locations to makefile
Compiling and linking fortran code with MakeFile using Intel compiler
How do I mark targets for remake using Open Watcom on the command line?
Target name in Makefile prerequisite
nvidia simpleDevLibCUBLAS error
Understanding deeply using a specific case how makefiles are interpreted
override_dh_auto_install doesn't run during debuild
Makefile always execute default command irrespctive of CFLAGS
dependency on default CMake target [duplicate]
Pattern rule with files in different directories?