X-Spam-Check-By:	sourceware.org
Message-ID:	<45E330B4.10507@portugalmail.pt>
Date:	Mon, 26 Feb 2007 19:10:44 +0000
From:	Pedro Alves <pedro_alves AT portugalmail DOT pt>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.1; pt-BR; rv:1.8.0.9) Gecko/20061207 Thunderbird/1.5.0.9 Mnenhy/0.7.4.0
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: /dev/null timing and clock skew problems
References:	<028f01c75931$4c090e80$0200a8c0 AT AMD2500> <20070226105032 DOT GB5577 AT calimero DOT vinschen DOT de>
In-Reply-To:	<20070226105032.GB5577@calimero.vinschen.de>
X-Antivirus:	avast! (VPS 000717-0, 26-02-2007), Outbound message
X-Antivirus-Status:	Clean
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

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/

- Raw text -