WSL2 - clock problems during build #4975
Description
Sorry if this duplicate - I tried to search and saw several messages which are referring to same/similar problem, however there seems to be no separate assigned recent entry tracking this particular problem. Mostly people complain about date being skewed (some workarounds are available) - this one however as far as I could tell has no workaround and is easily reproducible in the latest 2004 build, which make WSL 2 completely unsuitable for any real development use.
Windows 10 build 19041.153, attempting to use WSL2, files are on Windows file system (not rootfs):
-- Build files have been written to: /mnt/e/projects/misc/wsl-ssh-agent/release
make: Warning: File 'Makefile' has modification time 0.6 s in the future
make[1]: Warning: File 'CMakeFiles/Makefile2' has modification time 0.65 s in the future
make[2]: Warning: File 'CMakeFiles/bin_agent.dir/progress.make' has modification time 0.61 s in the future
Scanning dependencies of target bin_agent
make[2]: warning: Clock skew detected. Your build may be incomplete.
make[2]: Warning: File 'CMakeFiles/bin_agent.dir/progress.make' has modification time 0.51 s in the future
[100%] Building wsl-ssh-agent-gui...
make[2]: warning: Clock skew detected. Your build may be incomplete.
[100%] Built target bin_agent
make[1]: warning: Clock skew detected. Your build may be incomplete.
Could hv_utils: cannot register PTP clock: 0 be the reason for that?