It turns out it was my clock was set to 1997 and the file timestamps
were 1999. So I guess make had a little problem with that. Anyway,
I set my clock to the right time, and there seems to be no
problem anymore.
brian
On Sat, Feb 19, 2000 at 08:36:28AM -0800, Mike McCaskey wrote:
> it may be referring to rising/falling clock edges for bus timing,
> etc.....not necessarily the RTC.....could be a bad crystal?
>
> > -----Original Message-----
> > From: owner-lug-nuts@cheapnet.net [mailto:owner-lug-nuts@cheapnet.net]On
> > Behalf Of Brian Lavender
> > Sent: Saturday, February 19, 2000 3:44 AM
> > To: lug-nuts@saclug.org
> > Subject: [Lug-Nuts] clock skew detected
> >
> >
> > I just built a 400 K6-III system using an ASUS motherboard.
> > It fired up and it looks good. I went to compile the kernel
> > and it reported
> >
> > clock skew detected - build may be bad
> >
> > Is my clock drifting, or not keeping accurate enough time so
> > that make can't accurately judge the time? When the machine
> > is on, the clock does not depend upon the battery does it?
> >
> > Otherwise, it seems to be working fine.
> >
> > brian
> > --
> > Brian Lavender
> > http://www.brie.com/brian/
> > **********************************************************
> > * Sacramento Linux Users Group Mailing List
> > *
> > * Unsubscribe: Send a message to majordomo@saclug.org
> > * With 'unsubscribe lug-nuts' in the body
> > *
> > * http://www.saclug.org
> >
>
> **********************************************************
> * Sacramento Linux Users Group Mailing List
> *
> * Unsubscribe: Send a message to majordomo@saclug.org
> * With 'unsubscribe lug-nuts' in the body
> *
> * http://www.saclug.org
-- Brian Lavender http://www.brie.com/brian/ ********************************************************** * Sacramento Linux Users Group Mailing List * * Unsubscribe: Send a message to majordomo@saclug.org * With 'unsubscribe lug-nuts' in the body * * http://www.saclug.org
This archive was generated by hypermail 2b29 : Fri Feb 25 2000 - 14:29:12 PST