Date: Fri, 5 Jun 1998 10:25:42 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Daniel DeLorme <ddelorme AT ns DOT coba DOT net>
cc: djgpp AT delorie DOT com
Subject: Re: Help!! Installing Allegro
In-Reply-To: <3.0.3.32.19980604130847.0069be0c@ns.coba.net>
Message-ID: <Pine.SUN.3.91.980605101915.4137B-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Thu, 4 Jun 1998, Daniel DeLorme wrote:

> >make.exe:***File 'Makefile' has modification time in the future
> 
> if the modification time is in the future, you just have to set your
> system time even further in the future (if it was set right in the
> first place)

This might as well be caused by a known (but as yet unexplained) problem 
in latest versions of Windows 95: if you create a file and then stat it 
and compare the file time stamp to the system clock, the file's time 
stamp is up to 3 seconds newer (!).

Make complains about this because its algorithm of deciding whether to
rebuild a given file are based on such comparisons, and if system time 
and file times aren't in sync, Make will make wrong decisions.

This test is mainly meant for filesystems mounted over a network, due 
to time mismatch between different machines.  So if your files reside on 
a local drive, and if you are sure everything's fine with the way your 
system clock is set, just ignore this warning.  It is only a warning, 
Make doesn't change anything in its operation when it detects such clock 
skews.