Mail Archives: djgpp/1998/05/05/15:17:27
Anton Helm wrote:
>
> At 10:00 04.05.98 +0100, you wrote:
>
> >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 have some other experiences with "File has timestamp in the future":
>
> 1) I frequently copy my source codes between my PC and a unix host by
> means of SAMBA. I observed that the files I edited on the same day get
> a timestamp of **several hours in the future** when being copied to the
> unix host, while older file time stamps remain intact. This is either
> a problem in SAMBA or in WinNT4.0 (which I'm using on the PC).
> Running GNU make on the unix host will produce the above message.
This might be due to an unset TZ environment variable, thus one
machine assumes it runs on EDT, and the other on MESZ (or whatever).
If "several" means 7 or 8, this is a sure bet.
>
> 2) The second case was rather esoteric. I haven't managed to reproduce it
> yet but I have 3 witnesses whom I showed the following phenomenon:
> The system clock of WinNT4.0 and the time used in a DOS-box had a difference
> of 27 minutes, which resulted in the same error message. Rebooting the PC
> removed the 27 minutes "skew".
I don't know how far the DOS emulation go, it might be that it
looses timer interrupts, for whatever reasons. This should
go away when you open a new DOS box. Otherwise, it is just
inexplicable.
--
Ciao
Tom
*************************************************************
* Thomas Demmer *
* Lehrstuhl fuer Stroemungsmechanik *
* Ruhr-Uni-Bochum *
* Universitaetsstr. 150 *
* D-44780 Bochum *
* Tel: +49 234 700 6434 *
* Fax: +49 234 709 4162 *
* http://www.lstm.ruhr-uni-bochum.de/~demmer *
*************************************************************
- Raw text -