Sender: vheyndri AT rug DOT ac DOT be
Message-Id: <35459665.5E3F@rug.ac.be>
Date: Tue, 28 Apr 1998 10:42:13 +0200
From: Vik Heyndrickx <Vik DOT Heyndrickx AT rug DOT ac DOT be>
Mime-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: Clock skew detected, your build may be incomplete
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hi,

I think I found the reason why under Win95, sometimes, the messages
"Clock skew detected" and "Your build may be incomplete" are issued by
make.

It is a Winblows matter: Winblows make sure that the file's modification
time is larger than the file creation time. That means that a file
created on time C (seconds), and closed immediately, will get the
modification time C+1, even when the current time is still C and not C+1
yet.

That is speculation resulting from the following test:
I created two files from a batch file. Both files were created during
the same second, hence their creation time was the same, and so was
their modification time, however one more. I repeated these test by
making use of the INT21 functions, and experienced the same ``feature''.

The workaround is that users simply can ignore this message.
The only solution I have found to avoid this problem is using Linux
instead :-(
Any idea's someone?

The problem appears to be specific for OSR2 (Win 4.00.95b), maybe anyone
can confirm?

-- 
 \ Vik /-_-_-_-_-_-_/
  \___/ Heyndrickx /
   \ /-_-_-_-_-_-_/  Knight in the Order of the Unsigned Types