[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Clock skew detected

From: Paul D. Smith
Subject: Re: Clock skew detected
Date: Wed, 2 Apr 2003 10:47:30 -0500

%% gk <address@hidden> writes:

  g> make[1]: Warning: File 
  g> `/home/greg/xmake/test/XMakeSubProject1/XMakeSubProject2/XMakefile.mko' 
has modification time 1.1 s in the future
  g> make[1]: warning:  Clock skew detected.  Your build may be incomplete.

  g> After deleting the file, the same message happens again.

  g> I am running on the latest Cygwin with Windows 2000:
  g> * Red Hat Cygwin: cygwin1.dll version 1.3.22
  g>          + GNU bash, version 2.05.8(1)-release

  g> I compiled Gnu Make 3.80 from source, with patches applied for bugs
  g> 1516 and 1517. This version of Gnu Make has worked fine for months
  g> on my linux box; never saw this error before.

This error means the following:

  * Make ran a command to update a target
  * After the command completed, make examined the time last modified
    stamp on the target.
  * Make compared the TLM stamp to "now" (the current system clock) and
    determined that the TLM stamp was in the future (was greater than

In that case, make gives this warning.

If you work on a local filesystem you should never see this error.

If you work on a networked filesystem, you may well see it if the server
and client are not synced.

In Windows there is even a larger issue in that some Windows filesystems
don't keep TLM stamps with a 1 second granularity, so it's even worse!

  g> Is it possible Make was built incorrectly due to 'time' command not 
  g> installed at compile/config time?

No.  Make doesn't use the "time" command for anything and couldn't care
less whether it was installed or not.

 Paul D. Smith <address@hidden>          Find some GNU make tips at:            
 "Please remain calm...I may be mad, but I am a professional." --Mad Scientist

reply via email to

[Prev in Thread] Current Thread [Next in Thread]