Re: [Dev-C++] Timestamp out of range: substituing ....

[Alessandro B. <al...@vi...>]

I tried to modify the Delay Compile in Compiler Options from 0 ms to 500 ms,
but I obtain the same result.
Alessandro
----- Original Message ----- 
From: "Doug MacDonald" <dou...@al...>
To: "Alessandro Bugatti" <al...@vi...>
Cc: "Per Westermark" <pw...@ia...>;
<dev...@li...>
Sent: Monday, February 23, 2004 9:31 PM
Subject: Re: [Dev-C++] Timestamp out of range: substituing ....


> Check the posts of the past couple of weeks.  I'm sure I saw an exchange
> about this during that period.  I think there's a compiler setting in
> dev-c++ that someone was told to adjust because there was a small amount
> of jitter in the time stamps on files that occasionally caused make to
> complain.
>
> > No, all the sources are in local drive, and these messages are shown
> > only few times, but I don't understand why :-) Alessandro -----
> > Original Message ----- From: "Per Westermark" <pw...@ia...>
> > To: "Alessandro Bugatti" <al...@vi...> Cc:
> > <dev...@li...> Sent: Monday, February 23, 2004
> > 5:56 PM Subject: Re: [Dev-C++] Timestamp out of range: substituing
> > ....
> >
> >>> Do you keep your source on a networked drive? When building from
> >>> a networked drive, you might often get problems with file times,
> >>> since the make program is using the clock of the local machine,
> >>> but the newly created files will get the timestamp from the clock
> >>> on the server who owns the file system.
> >>>
> >>> /Per W
> >>>
> >>> On Mon, 23 Feb 2004, Alessandro Bugatti wrote:
> >>>
> >>
> >>>>> Hi all, this is not a real problem and it is not strictly
> >>>>> about DevCpp, but I
> >
> > don't know what happens and so I ask for someone knows.
> >
> >>>>> Sometimes when I compile the project I receive this 2
> >>>>> messages from the
> >
> > make.exe
> >
> >>>>> Timestamp out of range: substituing 1970:01:01 01:00:00
> >>>>> Timestamp out of range: substituing 1970:01:01 01:00:00
> >>>>> Looking at the Compile log it seems the compilation happens
> >>>>> three times
> >
> > and this is the reason for the messages. Then, why the compilation
> > happens three times?
> >
> >>>>>
> >>>>> Thanks in advance. Alessandro
>
>
>
>