updated CCACHE_NOUNIFY docs

diff --git a/ccache.1 b/ccache.1
index b9675b66383374cada74653ebac895f20b2711ec..d0e71433c187fe866e11a992e853b9b7da3e4083 100644 (file)
--- a/ccache.1
+++ b/ccache.1
@@ -145,7 +145,10 @@ CCACHE_NOUNIFY then ccache will not use the C/C++ unifier when hashing
 the pre-processor output\&. The unifier is slower than a normal hash, so
 setting this environment variable gains a little bit of speed, but it
 means that ccache can\&'t take advantage of not recompiling when the
-changes to the source code consist of reformatting only\&.
+changes to the source code consist of reformatting only\&. Note that
+using CCACHE_NOUNIFY changes the hash, so cached compiles with
+CCACHE_NOUNIFY set cannot be used when CCACHE_NOUNIFY is not set and
+vice versa\&.
 .IP 
 .PP 
 .SH "CACHE SIZE MANAGEMENT" 

diff --git a/ccache.yo b/ccache.yo
index 972eb1db297d041f3b79f56fdd9b49393134ec7d..8646cae0c461eb64df3fce0aea8db934848c2b35 100644 (file)
--- a/ccache.yo
+++ b/ccache.yo
@@ -123,7 +123,10 @@ CCACHE_NOUNIFY then ccache will not use the C/C++ unifier when hashing
 the pre-processor output. The unifier is slower than a normal hash, so
 setting this environment variable gains a little bit of speed, but it
 means that ccache can't take advantage of not recompiling when the
-changes to the source code consist of reformatting only.
+changes to the source code consist of reformatting only. Note that
+using CCACHE_NOUNIFY changes the hash, so cached compiles with
+CCACHE_NOUNIFY set cannot be used when CCACHE_NOUNIFY is not set and
+vice versa.
 
 enddit()
 

diff --git a/web/ccache-man.html b/web/ccache-man.html
index 91a5adb7eebb14b6d6ad7ccb1ae392e52056665c..b8b21aa2177fc08d05ae48a52b755ea3edbc73e5 100644 (file)
--- a/web/ccache-man.html
+++ b/web/ccache-man.html
@@ -121,7 +121,10 @@ CCACHE_NOUNIFY then ccache will not use the C/C++ unifier when hashing
 the pre-processor output. The unifier is slower than a normal hash, so
 setting this environment variable gains a little bit of speed, but it
 means that ccache can't take advantage of not recompiling when the
-changes to the source code consist of reformatting only.
+changes to the source code consist of reformatting only. Note that
+using CCACHE_NOUNIFY changes the hash, so cached compiles with
+CCACHE_NOUNIFY set cannot be used when CCACHE_NOUNIFY is not set and
+vice versa.
 <p></dl>
 <p><h2>CACHE SIZE MANAGEMENT</h2>