clock skew
Earnie Boyd
earnie_boyd@yahoo.com
Fri Apr 7 05:27:00 GMT 2000
--- Trevor Forbes <trevorforbes@ozemail.com.au> wrote:
> I get the following random error when building packages?
>
> make[1]: *** Warning: File `xmakefile' has modification time in the future
> (2000-04-07 08:09:32 > 2000-04-07 08:09:31)
> make[1]: *** Warning: Clock skew detected. Your build may be incomplete.
>
> The clock skew is always out by one second and it never seems to affect the
> final build.
> There is no network drives involved
>
>
> http://sourceware.cygnus.com/ml/cygwin/2000-02/msg00035.html
> states the problem as:
> This appears to be a typical characteristic of Windows systems, as if the
> low order bits of the file time are "random." It hasn't appeared to be a
> problem; I don't see it as often in Win2K. I've wondered whether cygwin
> should mask off the low order bits, given that Windows works this way.
>
> Is the above statement correct?
>
> Anyway, my question is, given that it does not seem to affect builds and
> that does not seem to be a common problem.
> Should I just continue to ignore the error or will it eventually cause a
> build to be incomplete?
>
>
Would you be using a networked device for storage, compilation, etc? This
could be a difference in clocks between your workstation and the fileserver.
=====
---
Earnie Boyd: < mailto:earnie_boyd@yahoo.com >
__Cygwin: POSIX on Windows__
Cygwin Newbies: < http://www.freeyellow.com/members5/gw32/index.html >
__Minimalist GNU for Windows__
Mingw32 List: < http://www.egroups.com/group/mingw32/ >
Mingw Home: < http://www.mingw.org/ >
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
More information about the Cygwin
mailing list