diff options
author | Paul Smith <psmith@gnu.org> | 2000-06-23 15:55:46 +0000 |
---|---|---|
committer | Paul Smith <psmith@gnu.org> | 2000-06-23 15:55:46 +0000 |
commit | fcbfe98cbe7d6332ee0673f685b280f7c019cd44 (patch) | |
tree | 59b557454953a9650f4f4795d5a5d0b5d50bc0dd /README.template | |
parent | cbe92a2241253145fbd11e32ed1f7efcb31ba91c (diff) | |
download | gunmake-fcbfe98cbe7d6332ee0673f685b280f7c019cd44.tar.gz |
* Fix -q so it works more correctly.
* Don't print "nothing to do" messages for ":" commands
* Update the version to 3.79.1
Diffstat (limited to 'README.template')
-rw-r--r-- | README.template | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/README.template b/README.template index f131fd6..6581046 100644 --- a/README.template +++ b/README.template @@ -121,3 +121,14 @@ files (LFS) in configure for those operating systems that provide it. Please report any bugs that you find in this area. If you run into difficulties, then as a workaround you should be able to disable LFS by adding the `--disable-largefile' option to the `configure' script. + +On systems that support micro- and nano-second timestamp values and +where stat(2) provides this information, GNU make will use it when +comparing timestamps to get the most accurate possible result. However, +at the moment there is no system call (that I'm aware of) that will +allow you to *set* a timestamp to a micro- or nano-second granularity. +This means that "cp -p" and other similar tools (tar, etc.) cannot +exactly duplicate timestamps with micro- and nano-second granularity. +If your build system contains rules that depend on proper behavior of +tools like "cp -p", you should configure make to not use micro- and +nano-second timestamps with the --disable-nsec-timestamps flag. |