From: kaih@khms.westfalen.de (Kai Henningsen)
To: linux-kernel@vger.kernel.org
Subject: Re: module mess in -CURRENT
Date: 15 Nov 2002 20:26:00 +0200 [thread overview]
Message-ID: <8$tgwO4mw-B@khms.westfalen.de> (raw)
In-Reply-To: <20021115043827.A20764@wotan.suse.de>
ak@suse.de (Andi Kleen) wrote on 15.11.02 in <20021115043827.A20764@wotan.suse.de>:
> > and then have the timer clear "xtime_count" every time it updates it.
>
> Problem is that you cannot easily synchronize such a monotonously increasing
> timer in a network. But make needs synchronized times.
That's really a make problem. It gets much worse when you count in times
going backwards because you restore a file from backup, or whatever.
What I'd really like make to do - but it can't with the current design -
is to note the exact time stamp of each dependency when creating a target,
and when reconsidering that target, finding out if any of those time
stamps have changed in any way (and, while we're at it, probably check the
size as well). *Changed since last time*, not younger than the target.
But of course to do that, you need a persistent repository for those time
stamps - which, I think, kbuild-Owen does.
If you think about the more tricky things to do with make, this is almost
always what you would need to make a solution much easier.
Take network time shift, for example. Once you no longer need a younger-
older relation, that time shift is actually completely irrelevant!
One of these days, when I have lots of time (as if!) ...
MfG Kai
next prev parent reply other threads:[~2002-11-15 19:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021114000206.A8245@infradead.org.suse.lists.linux.kernel>
[not found] ` <Pine.LNX.4.44.0211131655580.6810-100000@home.transmeta.com.suse.lists.linux.kernel>
2002-11-14 10:19 ` module mess in -CURRENT Andi Kleen
2002-11-14 17:32 ` John Alvord
2002-11-14 17:40 ` Andi Kleen
2002-11-14 18:01 ` Andrea Arcangeli
2002-11-14 18:18 ` Andi Kleen
2002-11-15 0:27 ` Jamie Lokier
2002-11-15 0:46 ` Linus Torvalds
2002-11-15 3:38 ` Andi Kleen
2002-11-15 18:26 ` Kai Henningsen [this message]
2002-11-15 18:14 ` Linux 2.5.47 -- Trouble booting Xwindows Mark Hamblin
2002-11-14 0:02 module mess in -CURRENT Christoph Hellwig
2002-11-14 0:59 ` Linus Torvalds
2002-11-14 1:05 ` Christoph Hellwig
2002-11-14 2:27 ` Alan Cox
2002-11-14 2:32 ` Linus Torvalds
2002-11-14 5:07 ` Rusty Russell
2002-11-14 4:36 ` Rusty Russell
2002-11-14 14:32 ` Alan Cox
2002-11-14 18:54 ` Roman Zippel
2002-11-14 4:06 ` Rusty Russell
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='8$tgwO4mw-B@khms.westfalen.de' \
--to=kaih@khms.westfalen.de \
--cc=linux-kernel@vger.kernel.org \
/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