From:	Shawn Hargreaves <Shawn AT talula DOT demon DOT co DOT uk>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Make "Clock Skew" problem.
Date:	Mon, 4 May 1998 10:00:20 +0100
Organization:	None
Message-ID:	<O1IUXCAkOYT1Ew2U@talula.demon.co.uk>
References:	<9804018940 DOT AA894039011 AT CCMAIL DOT NTSC DOT NAVY DOT MIL>
	<Pine DOT SUN DOT 3 DOT 91 DOT 980503181030 DOT 19706X-100000 AT is>
NNTP-Posting-Host:	talula.demon.co.uk
MIME-Version:	1.0
Lines:	33
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Eli Zaretskii writes:
>``Broken "make"'' and ``can't really use it'' seem like a wild
>exaggeration to me.

I've seen this problem a few times on my machine at work (p333, w95),
and it prints "File has timestamp in the future" and then aborts.
Running make again will work correctly, but it is slightly more than
just a warning. I agree that "broken" is perhaps too strong a word, but
it is annoying that I sometimes need to run make twice :-)

I've been wanting to look into this problem for a while, but I'm afraid
it is quite a low priority for me, so no promises if/when I will get
around to it...

>Besides, it's not Make that's broken, it's the Windows filesystem.

Absolutely. Or perhaps the DOS function call emulation is just returning
wrong data. If the internal 32 bit filesystem was in error, surely a lot
of native windows programs would have similar problems? The Visual C
make never seems to suffer from this trouble, but maybe it is just too
dumb to notice the bad times :-)

>Can somebody explain how could a filesystem set time stamps of files
>it creates to be 2 seconds in the future relative to the system clock,

Wild guess: perhaps the time is set according to when the cache is
flushed to disk, rather than when the data was actually written by the
program?


--
Shawn Hargreaves - shawn AT talula DOT demon DOT co DOT uk - http://www.talula.demon.co.uk/
"Pigs use it for a tambourine" - Frank Zappa

- Raw text -