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?
Makefile rebuilds all files even if only one changes
Variable expansion in Makefile
basic makefile ifeq how to
Exists a better way to resolve target depencies in makefile?
Turn “overriding commands for target” into error
How to make configurable makefile and optional configuration for certain files?
sdcc Makefile for 8051 microcontrollers
Make doesn't finish when run with entr
Why does the `shell` command in Make remove newlines?
Make missing separator issue
Makefile always compile no mater new or old
Splint : Cannot open file
Pairing same-index items in two lists as target and dependency in makefile
unrecognized command line option '-std=c++11' using mitlm
Forward command-line arguments to Makefile
Wildcard expansion for a pattern recipe