/dev/null timing and clock skew problems

[Pedro Alves]

Corinna Vinschen escreveu:
> 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.
> 

You are saying this should only happen on devices?  I see this a lot on
regular files.

I just got this:
make: Warning: File `Makefile' has modification time 0.42 s in the future

Cheers,
Pedro Alves


--
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/