P.S., regarding the documentation of `.LOW_RESOLUTION_TIME'
Here with GNU Make 3.81, I think you should not blame the cp command,
but instead say "when using a mixture of filesystem types, or in some
other situations, one might want to specify some files were made with
low resolution timestamps..."
> "EZ" == Eli Zaretskii writes:
EZ> What's wrong with using the special target .LOW_RESOLUTION_TIME?
One cannot find it with searches for "seconds" "comparison" etc.
OK, thanks! Please add a cross reference to it on many of the places where
(Info-search "modification") is mentioned. Thanks.
> From: jida...@jidanni.org
> Date: Thu, 02 Dec 2010 10:13:31 +0800
> Cc: bug-make@gnu.org
>
> > "PS" == Paul Smith writes:
>
> PS> Make already uses high-resolution timestamps for comparison
> PS> automatically on filesystems that support it, if that's what you
> PS> mean.
>
> That's the p
> "PS" == Paul Smith writes:
PS> Make already uses high-resolution timestamps for comparison
PS> automatically on filesystems that support it, if that's what you
PS> mean.
That's the problem, when two different resolution filesystems are
involved, make will always see these,
$ ls -l /tmp/zao
On Thu, 2010-12-02 at 08:41 +0800, jida...@jidanni.org wrote:
> By the way, make(1) lacks any of this time comparison resolution
> machinery at all! I'll CC them.
Can you be more clear? What is the behavior you are missing today, that
you would like to have?
I'm not following how this feature of
