Date: Mon, 4 May 1998 10:40:46 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Nate Eldredge <nate AT cartsys DOT com>
cc: ROBERT_FINLEY AT ntsc DOT navy DOT mil, djgpp AT delorie DOT com
Subject: Re: Make "Clock Skew" problem.
In-Reply-To: <19980503165659.AAB13333@ppp122.cartsys.com>
Message-ID: <Pine.SUN.3.91.980504104021.23844A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Sun, 3 May 1998, Nate Eldredge wrote:

> ! 	if (mtime > now && (((mtime % 2) == 0) && ((mtime-3) > now)))

For a quick hack, I'd suggest to leave only the second part of the
test:
	if (mtime > now + 3)

But, if you think about this for a moment, you will realize that using
Make on a filesystem which lies up to 3 seconds about the file times
might totally disrupt the operation of Make.  Shutting up the warning
is tantamount to killing the messenger in this case: the problem
doesn't go away because you look the other way.

That is why I'm still thinking about the right way to solve this
problem.  Assuming all the files are on the same filesystem which has
the same time skew, I can solve this fairly easy.  But that assumption
will surely break in some cases, so Make will probably need to
maintain the skew value for each filesystem and apply it when checking
file times.

I also haven't given up hope that somebody will come up with a
reasonable explanation of why does this madness at all happen, and
that using that explanation we could find a better solution.