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?
setting variable with eval in Makefile recipe
make: .SECONDARY target breaks buld
Makefile: converting multiple .dot files to .png
What does “$(#:%.o=%.d)” mean in a makefile?
pass a value from one makefile target to another
Why my Makefile auto-dependencies does not work
Multiple service starting with make inside docker-compose
Simple Makefile doesn't clean
Adding a library file into a binary file
FORTRAN Makefile for a large project
How to add new file types to Makefile?
Single make rule for multiple output files in different directories
Error while loading shared libraries: liblua.so
CMake autogenerated Makefile on ubuntu 16.04 docker image prepending “//” to targets
How Makefile split string into individual words?
if statement in ONESHELL Makefile not working