Problems compiling due to clock skew

[Thom]

I tried the clean target and find / touch, neither resolved the issue.

I think you pointed me in the right direction tho. Compiling on a virtualBox VM using Vagrant, which shares a host folder with VM, and that's where the compile is taking place.

I'll try moving the source tree off the shared folder and onto the native VM disk to see if that fixes it.

Thx BM  8)

That fixed it. I have observed that VM platforms don't perform well when it comes to shared disk resources. Not only is the timestamp problem resolved but the build takes a fraction of the time it did using the shared drive.

[bytemaster]

If you are building on a network drive that could be the issue. 

Also if your clock changed while you were compiling it could be an issue.

make clean; make should fix any potential issues.

[Thom]

Linking C static library libeasylzma_static.a
make[2]: warning:  Clock skew detected.  Your build may be incomplete.
[ 24%] Built target easylzma_static
Scanning dependencies of target fc
make[2]: Warning: File `libraries/fc/CMakeFiles/fc.dir/depend.make' has modification time 2.2 s in the future

I tried this at the top of the build tree: find . -type f | xargs -n 5 touch but it still occurs. I googled the issue but can't find the actual cause. Most say they resolved the problem with a clean / touch.