This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: /dev/null timing and clock skew problems
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 26 Feb 2007 11:50:32 +0100
- Subject: Re: /dev/null timing and clock skew problems
- References: <028f01c75931$4c090e80$0200a8c0@AMD2500>
- Reply-to: cygwin at cygwin dot com
On Feb 25 23:04, Aaron Gray wrote:
> I am doing make based builds on Cygwin and am getting following warning
> messages multiple times in stdout :-
>
> make[2]: Warning: File `/dev/null' has modification time 0.0096 s in
> the future
>
> make[2]: warning: Clock skew detected. Your build may be
> incomplete.
>
> I am using Windows XP.
>
> Anyone know what is going on and how to correct it ?
/dev/null's timestamps are faked since /dev/null is just another name
for the Windows NUL device (or rather, NT's \Device\Null device). The
timestamps you get from stat() are just the current system time,
converted into a file time. This can result in conversion inaccuracy,
apparently. Nothing we can do against for the current release. Remove
the check against /dev/null or convert it to a check against some other
random file. I'm wondering what this is supposed to do anyway.
In the long run, maybe it would be better in Cygwin to set the timestamp
for devices to epoch.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/