From: Michal Marek <mmarek@suse.cz>
To: Nishanth Aravamudan <nacc@linux.vnet.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-kbuild@vger.kernel.org
Subject: Re: `make dep' with clock skew detected loops forever
Date: Mon, 05 Mar 2012 15:40:56 +0100 [thread overview]
Message-ID: <4F54D078.9050608@suse.cz> (raw)
In-Reply-To: <20120229190138.GG5136@linux.vnet.ibm.com>
On 29.2.2012 20:01, Nishanth Aravamudan wrote:
> Noticed something on a fresh FC16 based install on a test server in our
> lab. Autotest by default runs `make dep` and it seems the clock is
> pretty badly skewed on this server, resulting in an infinite loop of:
>
> 01:09:37 DEBUG| Running 'make dep'
> 01:09:38 DEBUG| [stderr] make: Warning: File `/usr/local/autotest/tmp/build/linux/arch/powerpc/Makefile' has modification time 112143 s in the future
> 01:09:38 DEBUG| [stderr] make[1]: Warning: File `/usr/local/autotest/tmp/build/linux/arch/powerpc/Makefile' has modification time 112143 s in the future
> 01:09:38 DEBUG| [stderr] make[2]: Warning: File `scripts/Makefile.host' has modification time 112143 s in the future
> 01:09:38 DEBUG| [stdout] HOSTCC scripts/basic/fixdep
> 01:09:38 DEBUG| [stderr] make[2]: warning: Clock skew detected. Your build may be incomplete.
> 01:09:38 DEBUG| [stderr] make[2]: Warning: File `scripts/Makefile.host' has modification time 112143 s in the future
[...]
> Anyone know why that happens?
Because the system time time is several hours, if not days, behind, so
generated files are older than source files and thus dependencies cannot
work. You need to fix the system time to be at least ahead of the mtime
of the sources.
> Obvious fixes are to either not run `make dep`
I don't think this is limited to make dep.
Michal
next prev parent reply other threads:[~2012-03-05 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 19:01 `make dep' with clock skew detected loops forever Nishanth Aravamudan
2012-03-05 14:40 ` Michal Marek [this message]
2012-03-05 15:33 ` Nishanth Aravamudan
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=4F54D078.9050608@suse.cz \
--to=mmarek@suse.cz \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nacc@linux.vnet.ibm.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