From: Mikael Pettersson <mikpe@csd.uu.se>
To: linux-kernel@vger.kernel.org, tmolina@home.com
Cc: sensors@stimpy.netroedge.com
Subject: Re: time in the future during make for 2.4.0
Date: Sun, 28 Jan 2001 20:49:38 +0100 (MET) [thread overview]
Message-ID: <200101281949.UAA11123@harpo.it.uu.se> (raw)
On Sun, 28 Jan 2001 12:27:46 -0600 (CST), Thomas Molina wrote:
>I seem to recall a discussion on faster processors causing timing
>problems during a kernel make, but I'm unable to find it in the kernel
>archives. I've now upgraded to an Athlon 900 MHz processor and an ASUS
>A7V motherboard and have started seeing this. It shows up as the
>following messages during a make bzImage:
>
>make[3]: *** Warning: Clock skew detected. Your build may be
>incomplete.
>make[3]: *** Warning: File
>`/mnt/hd/local/kernel/linux.24.new/include/linux/sched.h' has
>modification time in the future (2001-01-28 17:41:05 > 2001-01-28
>10:07:02)
No, this doesn't look like the "fast CPU" problem you are alluding to
(look for subject MODVERSIONS in the archives). We fixed that one.
Your problem is that your kernel source dir (unpacked tarball?)
contains files with time stamps several hours in the future;
'make' doesn't take kindly to this.
I've seen this happen once: during an upgrade (RH-style, i.e. not
fresh install) from RH6.2 to RH7.0, my /etc/localtime had become
overwritten and my machine in an instant moved from CET to some US
time zone 6 or 8 hrs back. Then when I unpacked my kernel tarball to
build a real kernel, I got exactly the problems you listed above.
Check your clock & time zone settings.
/Mikael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-28 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-28 19:49 Mikael Pettersson [this message]
2001-01-28 19:56 ` phil
2001-01-28 21:00 ` Thomas Molina
-- strict thread matches above, loose matches on Subject: below --
2001-01-28 18:27 Thomas Molina
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=200101281949.UAA11123@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=linux-kernel@vger.kernel.org \
--cc=sensors@stimpy.netroedge.com \
--cc=tmolina@home.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
all inboxes | Powered by JetHome®