public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Trevor Forbes" <trevorforbes@ozemail.com.au>
To: "Cygwin" <cygwin@sourceware.cygnus.com>
Subject: Re: clock skew
Date: Fri, 07 Apr 2000 16:47:00 -0000	[thread overview]
Message-ID: <002e01bfa0eb$8b58e200$0200a8c0@VOYAGER> (raw)
In-Reply-To: <20000407122733.21078.qmail@web113.yahoomail.com>

----- Original Message -----
From: "Earnie Boyd" <earnie_boyd@yahoo.com>
To: "Trevor Forbes" <trevorforbes@ozemail.com.au>; "Cygwin"
<cygwin@sourceware.cygnus.com>
Sent: Friday, 7 April 2000 9:57
Subject: Re: clock skew


> --- Trevor Forbes <trevorforbes@ozemail.com.au> wrote:
> > I get  the following random error when building packages?
> >
> > make[1]: *** Warning: File `xmakefile' has modification time in the
future
> > (2000-04-07 08:09:32 > 2000-04-07 08:09:31)
> > make[1]: *** Warning:  Clock skew detected.  Your build may be
incomplete.
> >
> > The clock skew is always out by one second and it never seems to affect
the
> > final build.
> > There is no network drives involved
> >
> >
> > http://sourceware.cygnus.com/ml/cygwin/2000-02/msg00035.html
> > states the problem as:
> > This appears to be a typical characteristic of Windows systems, as if
the
> > low order bits of the file time are "random."  It hasn't appeared to be
a
> > problem; I don't see it as often in Win2K.  I've wondered whether cygwin
> > should mask off the low order bits, given that Windows works this way.
> >
> > Is the above statement correct?
> >
> > Anyway, my question is, given that it does not seem to affect builds and
> > that does not seem to be a common problem.
> > Should I just continue to ignore the error or will it eventually cause a
> > build to be incomplete?
> >
> >
>
> Would you be using a networked device for storage, compilation, etc?  This
> could be a difference in clocks between your workstation and the
fileserver.
>
>
> =====
> ---
>    Earnie Boyd: < mailto:earnie_boyd@yahoo.com >
>             __Cygwin: POSIX on Windows__
> Cygwin Newbies: < http://www.freeyellow.com/members5/gw32/index.html >
>            __Minimalist GNU for Windows__
>   Mingw32 List: < http://www.egroups.com/group/mingw32/ >
>     Mingw Home: < http://www.mingw.org/ >
>
> __________________________________________________
> Do You Yahoo!?
> Talk to your friends online with Yahoo! Messenger.
> http://im.yahoo.com
>

Simply no.



Trevor



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

  parent reply	other threads:[~2000-04-07 16:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-07  5:27 Earnie Boyd
2000-04-07  8:30 ` Tim Prince
2000-04-07 16:47 ` Trevor Forbes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-04-06 16:52 Trevor Forbes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='002e01bfa0eb$8b58e200$0200a8c0@VOYAGER' \
    --to=trevorforbes@ozemail.com.au \
    --cc=cygwin@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).