From tlumley@u.washington.edu  Tue Nov 13 18:25:59 2001
From: tlumley@u.washington.edu (Thomas Lumley)
Date: Tue, 13 Nov 2001 10:25:59 -0800 (PST)
Subject: [Rd] modification time warning with R CMD check
In-Reply-To: <15345.24656.694686.421844@gargle.gargle.HOWL>
Message-ID: <Pine.A41.4.33.0111131021490.38952-100000@homer33.u.washington.edu>

On Tue, 13 Nov 2001, David Kane  <David Kane wrote:

> I often get warnings like the following when running R CMD check
>
> [...]
> * checking for code/documentation mismatches ... OK
> * checking tests ...
> make: *** Warning: File `Makevars' has modification time in the future (2001-11-13 12:54:37.381546042 > 2001-11-13 12:54:37.314975985)
> [...]
>
> I am ready to believe that this is not a bug (i.e., that the timing on my
> various machines and file systems is such that I am creating a Makevars with a
> modification that is 0.07 seconds in the future from the perspective of the
> machine that Perl is running on). However, I would think that a
> warning would only be justified if this were far enough (1 second? 5 seconds?)
> in the future to be "interesting".

I get this too from time to time.  It's actually hard to tell what is
'uninteresting' in general. For example, Linux can create a file in about
50 microseconds on suitable hardware, so a 0.07s lag is easily enough that
files might in principle have been created in the wrong order, messing up
the make algorithm.

Fortunately in building R this sort of lag doesn't matter.
Unfortunately I don't know how to turn the warning off.

	-thomas

-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
Send "info", "help", or "[un]subscribe"
(in the "body", not the subject !)  To: r-devel-request@stat.math.ethz.ch
_._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._


[Rd] modification time warning with R CMD check
Thomas Lumley