Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: Bill Currie <bill AT taniwha DOT tssc DOT co DOT nz>,
        Vik Heyndrickx <Vik DOT Heyndrickx AT rug DOT ac DOT be>
From: Nate Eldredge <nate AT cartsys DOT com>
Subject: Re: Clock skew detected, your build may be incomplete
Cc: djgpp-workers AT delorie DOT com
Date: Tue, 28 Apr 1998 20:37:35 -0700
Message-ID: <19980429033703.AAG3301@ppp104.cartsys.com>
Precedence: bulk

At 10:32  4/28/1998 +1200, Bill Currie wrote:
>Vik Heyndrickx wrote:
>> The workaround is that users simply can ignore this message.
>> The only solution I have found to avoid this problem is using Linux
>> instead :-(
>
>Why frown? :)
>
>> Any idea's someone?
>
>I wouldn't be surprised if Eli suggests this as well, but what about
>hacking make (dos build only of course), to allow the present to extend
>one (or is it two? DOS only encodes every second second (bletch, what a
>phrase:)) seconds into the future, thus skipping this.  I don't think
>this will cause cyclic builds, but I guess it would need very thourough
>testing.  However, I never hand such problems when make complained about
>the time stamps.

Or:

When `make' detects such an error, have it sleep for two seconds and try again?

It has the advantage of simplicity, though not of efficiency. :(

Nate Eldredge
nate AT cartsys DOT com



wer, but at least it assures compatibility. Any
>thoughts?

"Little" is quite an understatement here.

Nate Eldredge
nate AT cartsys DOT com