問題：
[ 92%] Building C object CMakeFiles/dyna.x.dir/mystrings/StrEdit.c.o
[100%] Building C object CMakeFiles/dyna.x.dir/mystrings/mystring.c.o
Linking C executable dyna.x
make[1]: Warning: File `StrEdit.c' has modification time 36 s in the future
make[2]: warning: Clock skew detected. Your build may be incomplete.
原因：
in regards to the below warning...
Warning message: Clock skew detected. Your build may be incomplete.
These warnings can occur when the clock on the build machine is out of sync with the timestamps on the source files. Other errors, apparently unrelated but in fact caused by the clock skew, can occur along with the clock skew warnings. These secondary errors may tend to obscure the fact that the true root cause of the problem is an out-of-sync clock. For example, an out-of-sync clock has been known to cause an old version of javac to be used to compile some files, resulting in errors when the pre-1.4 compiler ran across the new assert keyword in the 1.4 source code.
If you see these warnings, reset the clock on the build machine, run "gnumake clobber" or delete the directory containing the build output, and restart the build from the beginning.
解決：
find . -type f | xargs -n 5 touch
make clean
[ 92%] Building C object CMakeFiles/dyna.x.dir/mystrings/StrEdit.c.o
[100%] Building C object CMakeFiles/dyna.x.dir/mystrings/mystring.c.o
Linking C executable dyna.x
make[1]: Warning: File `StrEdit.c' has modification time 36 s in the future
make[2]: warning: Clock skew detected. Your build may be incomplete.
原因：
in regards to the below warning...
Warning message: Clock skew detected. Your build may be incomplete.
These warnings can occur when the clock on the build machine is out of sync with the timestamps on the source files. Other errors, apparently unrelated but in fact caused by the clock skew, can occur along with the clock skew warnings. These secondary errors may tend to obscure the fact that the true root cause of the problem is an out-of-sync clock. For example, an out-of-sync clock has been known to cause an old version of javac to be used to compile some files, resulting in errors when the pre-1.4 compiler ran across the new assert keyword in the 1.4 source code.
If you see these warnings, reset the clock on the build machine, run "gnumake clobber" or delete the directory containing the build output, and restart the build from the beginning.
解決：
find . -type f | xargs -n 5 touch
make clean
make
轉自：http://blog.chinaunix.net/uid-20789721-id-470971.html
