3 .\" Author: [see the "Author" section]
4 .\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
6 .\" Manual: ccache Manual
7 .\" Source: ccache 3.5.1
10 .TH "CCACHE" "1" "01/03/2019" "ccache 3\&.5\&.1" "ccache Manual"
11 .\" -----------------------------------------------------------------
12 .\" * Define some portability stuff
13 .\" -----------------------------------------------------------------
14 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
15 .\" http://bugs.debian.org/507673
16 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
17 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
20 .\" -----------------------------------------------------------------
21 .\" * set default formatting
22 .\" -----------------------------------------------------------------
23 .\" disable hyphenation
25 .\" disable justification (adjust text to left margin only)
27 .\" -----------------------------------------------------------------
28 .\" * MAIN CONTENT STARTS HERE *
29 .\" -----------------------------------------------------------------
31 ccache \- a fast C/C++ compiler cache
35 \fBccache\fR [\fIoptions\fR]
36 \fBccache\fR \fIcompiler\fR [\fIcompiler options\fR]
37 \fIcompiler\fR [\fIcompiler options\fR] (via symbolic link)
41 ccache is a compiler cache\&. It speeds up recompilation by caching the result of previous compilations and detecting when the same compilation is being done again\&. Supported languages are C, C++, Objective\-C and Objective\-C++\&.
43 ccache has been carefully written to always produce exactly the same compiler output that you would get without the cache\&. The only way you should be able to tell that you are using ccache is the speed\&. Currently known exceptions to this goal are listed under CAVEATS\&. If you ever discover an undocumented case where ccache changes the output of your compiler, please let us know\&.
54 Keeps statistics on hits/misses\&.
65 Automatic cache size management\&.
76 Can cache compilations that generate warnings\&.
109 Optionally compresses files in the cache to reduce disk space\&.
121 Only knows how to cache the compilation of a single C/C++/Objective\-C/Objective\-C++ file\&. Other types of compilations (multi\-file compilation, linking, etc) will silently fall back to running the real compiler\&.
132 Only works with GCC and compilers that behave similar enough\&.
143 Some compiler flags are not supported\&. If such a flag is detected, ccache will silently fall back to running the real compiler\&.
147 There are two ways to use ccache\&. You can either prefix your compilation commands with \fBccache\fR or you can let ccache masquerade as the compiler by creating a symbolic link (named as the compiler) to ccache\&. The first method is most convenient if you just want to try out ccache or wish to use it for some specific projects\&. The second method is most useful for when you wish to use ccache for all your compilations\&.
149 To use the first method, just make sure that \fBccache\fR is in your \fBPATH\fR\&.
151 To use the symlinks method, do something like this:
157 cp ccache /usr/local/bin/
158 ln \-s ccache /usr/local/bin/gcc
159 ln \-s ccache /usr/local/bin/g++
160 ln \-s ccache /usr/local/bin/cc
161 ln \-s ccache /usr/local/bin/c++
167 And so forth\&. This will work as long as the directory with symlinks comes before the path to the compiler (which is usually in \fB/usr/bin\fR)\&. After installing you may wish to run \(lqwhich gcc\(rq to make sure that the correct link is being used\&.
173 .nr an-no-space-flag 1
181 The technique of letting ccache masquerade as the compiler works well, but currently doesn\(cqt interact well with other tools that do the same thing\&. See USING CCACHE WITH OTHER COMPILER WRAPPERS\&.
189 .nr an-no-space-flag 1
197 Do not use a hard link, use a symbolic link\&. A hard link will cause \(lqinteresting\(rq problems\&.
202 These options only apply when you invoke ccache as \(lqccache\(rq\&. When invoked as a compiler (via a symlink as described in the previous section), the normal compiler options apply and you should refer to the compiler\(cqs documentation\&.
204 \fB\fB\-c, \-\-cleanup\fR\fR
206 Clean up the cache by removing old cached files until the specified file number and cache size limits are not exceeded\&. This also recalculates the cache file count and size totals\&. Normally, there is no need to initiate cleanup manually as ccache keeps the cache below the specified limits at runtime and keeps statistics up to date on each compilation\&. Forcing a cleanup is mostly useful if you manually modify the cache contents or believe that the cache size statistics may be inaccurate\&.
209 \fB\fB\-C, \-\-clear\fR\fR
211 Clear the entire cache, removing all cached files, but keeping the configuration file\&.
214 \fB\fB\-F, \-\-max\-files\fR\fR=\fIN\fR
216 Set the maximum number of files allowed in the cache\&. Use 0 for no limit\&. The value is stored in a configuration file in the cache directory and applies to all future compilations\&.
219 \fB\fB\-h, \-\-help\fR\fR
221 Print an options summary page\&.
224 \fB\fB\-M, \-\-max\-size\fR\fR=\fISIZE\fR
226 Set the maximum size of the files stored in the cache\&.
228 should be a number followed by an optional suffix: k, M, G, T (decimal), Ki, Mi, Gi or Ti (binary)\&. The default suffix is G\&. Use 0 for no limit\&. The value is stored in a configuration file in the cache directory and applies to all future compilations\&.
231 \fB\fB\-o, \-\-set\-config\fR\fR=\fIKEY=VALUE\fR
238 for more information\&.
241 \fB\fB\-p, \-\-print\-config\fR\fR
243 Print current configuration options and from where they originate (environment variable, configuration file or compile\-time default)\&.
246 \fB\fB\-s, \-\-show\-stats\fR\fR
248 Print the current statistics summary for the cache\&.
251 \fB\fB\-V, \-\-version\fR\fR
253 Print version and copyright information\&.
256 \fB\fB\-z, \-\-zero\-stats\fR\fR
258 Zero the cache statistics (but not the configuration options)\&.
262 When run as a compiler, ccache usually just takes the same command line options as the compiler you are using\&. The only exception to this is the option \fB\-\-ccache\-skip\fR\&. That option can be used to tell ccache to avoid interpreting the next option in any way and to pass it along to the compiler as\-is\&.
268 .nr an-no-space-flag 1
276 \fB\-\-ccache\-skip\fR currently only tells ccache not to interpret the next option as a special compiler option \(em the option will still be included in the direct mode hash\&.
280 The reason this can be important is that ccache does need to parse the command line and determine what is an input filename and what is a compiler option, as it needs the input filename to determine the name of the resulting object file (among other things)\&. The heuristic ccache uses when parsing the command line is that any argument that exists as a file is treated as an input file name\&. By using \fB\-\-ccache\-skip\fR you can force an option to not be treated as an input file name and instead be passed along to the compiler as a command line option\&.
282 Another case where \fB\-\-ccache\-skip\fR can be useful is if ccache interprets an option specially but shouldn\(cqt, since the option has another meaning for your compiler than what ccache thinks\&.
285 ccache\(cqs default behavior can be overridden by configuration file settings, which in turn can be overridden by environment variables with names starting with \fBCCACHE_\fR\&. ccache normally reads configuration from two files: first a system\-level configuration file and secondly a cache\-specific configuration file\&. The priority of configuration settings is as follows (where 1 is highest):
295 Environment variables\&.
306 The cache\-specific configuration file
307 \fB\fI<ccachedir>\fR\fR\fB/ccache\&.conf\fR
309 \fB$HOME/\&.ccache/ccache\&.conf\fR)\&.
320 The system\-wide configuration file
321 \fB\fI<sysconfdir>\fR\fR\fB/ccache\&.conf\fR
323 \fB/etc/ccache\&.conf\fR
325 \fB/usr/local/etc/ccache\&.conf\fR)\&.
336 Compile\-time defaults\&.
339 As a special case, if the environment variable \fBCCACHE_CONFIGPATH\fR is set, ccache reads configuration from the specified path instead of the default paths\&.
340 .SS "Configuration file syntax"
342 Configuration files are in a simple \(lqkey = value\(rq format, one setting per line\&. Lines starting with a hash sign are comments\&. Blank lines are ignored, as is whitespace surrounding keys and values\&. Example:
348 # Set maximum cache size to 10 GB:
356 Some settings are boolean values (i\&.e\&. truth values)\&. In a configuration file, such values must be set to the string \fBtrue\fR or \fBfalse\fR\&. For the corresponding environment variables, the semantics are a bit different: a set environment variable means \(lqtrue\(rq (even if set to the empty string), the following case\-insensitive negative values are considered an error (rather than surprising the user): \fB0\fR, \fBfalse\fR, \fBdisable\fR and \fBno\fR, and an unset environment variable means \(lqfalse\(rq\&. Each boolean environment variable also has a negated form starting with \fBCCACHE_NO\fR\&. For example, \fBCCACHE_COMPRESS\fR can be set to force compression and \fBCCACHE_NOCOMPRESS\fR can be set to force no compression\&.
357 .SS "Configuration settings"
359 Below is a list of available configuration settings\&. The corresponding environment variable name is indicated in parentheses after each configuration setting key\&.
361 \fBbase_dir\fR (\fBCCACHE_BASEDIR\fR)
363 This setting should be an absolute path to a directory\&. ccache then rewrites absolute paths into relative paths before computing the hash that identifies the compilation, but only for paths under the specified directory\&. If set to the empty string (which is the default), no rewriting is done\&. A typical path to use as the base directory is your home directory or another directory that is a parent of your build directories\&. Don\(cqt use
365 as the base directory since that will make ccache also rewrite paths to system header files, which doesn\(cqt gain anything\&.
367 See also the discussion under
368 COMPILING IN DIFFERENT DIRECTORIES\&.
371 \fBcache_dir\fR (\fBCCACHE_DIR\fR)
373 This setting specifies where ccache will keep its cached compiler outputs\&. It will only take effect if set in the system\-wide configuration file or as an environment variable\&. The default is
374 \fB$HOME/\&.ccache\fR\&.
377 \fBcache_dir_levels\fR (\fBCCACHE_NLEVELS\fR)
379 This setting allows you to choose the number of directory levels in the cache directory\&. The default is 2\&. The minimum is 1 and the maximum is 8\&.
382 \fBcompiler\fR (\fBCCACHE_COMPILER\fR or (deprecated) \fBCCACHE_CC\fR)
384 This setting can be used to force the name of the compiler to use\&. If set to the empty string (which is the default), ccache works it out from the command line\&.
387 \fBcompiler_check\fR (\fBCCACHE_COMPILERCHECK\fR)
389 By default, ccache includes the modification time (\(lqmtime\(rq) and size of the compiler in the hash to ensure that results retrieved from the cache are accurate\&. This setting can be used to select another strategy\&. Possible values are:
393 Hash the content of the compiler binary\&. This makes ccache very slightly slower compared to the
395 setting, but makes it cope better with compiler upgrades during a build bootstrapping process\&.
400 Hash the compiler\(cqs mtime and size, which is fast\&. This is the default\&.
405 Don\(cqt hash anything\&. This may be good for situations where you can safely use the cached results even though the compiler\(cqs mtime or size has changed (e\&.g\&. if the compiler is built as part of your build system and the compiler\(cqs source has not changed, or if the compiler only has changes that don\(cqt affect code generation)\&. You should only use the
407 setting if you know what you are doing\&.
414 as the string to calculate hash from\&. This can be the compiler revision number you retrieved earlier and set here via environment variable\&.
417 \fIa command string\fR
419 Hash the standard output and standard error output of the specified command\&. The string will be split on whitespace to find out the command and arguments to run\&. No other interpretation of the command string will be done, except that the special word
421 will be replaced with the path to the compiler\&. Several commands can be specified with semicolon as separator\&. Examples:
437 %compiler% \-dumpmachine; %compiler% \-dumpversion
443 You should make sure that the specified command is as fast as possible since it will be run once for each ccache invocation\&.
445 Identifying the compiler using a command is useful if you want to avoid cache misses when the compiler has been rebuilt but not changed\&.
447 Another case is when the compiler (as seen by ccache) actually isn\(cqt the real compiler but another compiler wrapper \(em in that case, the default
449 method will hash the mtime and size of the other compiler wrapper, which means that ccache won\(cqt be able to detect a compiler upgrade\&. Using a suitable command to identify the compiler is thus safer, but it\(cqs also slower, so you should consider continue using the
451 method in combination with the
453 setting if possible\&. See
454 USING CCACHE WITH OTHER COMPILER WRAPPERS\&.
458 \fBcompression\fR (\fBCCACHE_COMPRESS\fR or \fBCCACHE_NOCOMPRESS\fR, see Boolean values above)
460 If true, ccache will compress object files and other compiler output it puts in the cache\&. However, this setting has no effect on how files are retrieved from the cache; compressed and uncompressed results will still be usable regardless of this setting\&. The default is false\&.
463 \fBcompression_level\fR (\fBCCACHE_COMPRESSLEVEL\fR)
465 This setting determines the level at which ccache will compress object files\&. It only has effect if
467 is enabled\&. The value defaults to 6, and must be no lower than 1 (fastest, worst compression) and no higher than 9 (slowest, best compression)\&.
470 \fBcpp_extension\fR (\fBCCACHE_EXTENSION\fR)
472 This setting can be used to force a certain extension for the intermediate preprocessed file\&. The default is to automatically determine the extension to use for intermediate preprocessor files based on the type of file being compiled, but that sometimes doesn\(cqt work\&. For example, when using the \(lqaCC\(rq compiler on HP\-UX, set the cpp extension to
476 \fBdebug\fR (\fBCCACHE_DEBUG\fR or \fBCCACHE_NODEBUG\fR, see Boolean values above)
478 If true, enable the debug mode\&. The debug mode creates per\-object debug files that are helpful when debugging unexpected cache misses\&. Note however that ccache performance will be reduced slightly\&. See
480 for more information\&. The default is false\&.
483 \fBdirect_mode\fR (\fBCCACHE_DIRECT\fR or \fBCCACHE_NODIRECT\fR, see Boolean values above)
485 If true, the direct mode will be used\&. The default is true\&. See
489 \fBdisable\fR (\fBCCACHE_DISABLE\fR or \fBCCACHE_NODISABLE\fR, see Boolean values above)
491 When true, ccache will just call the real compiler, bypassing the cache completely\&. The default is false\&.
494 \fBextra_files_to_hash\fR (\fBCCACHE_EXTRAFILES\fR)
496 This setting is a list of paths to files that ccache will include in the the hash sum that identifies the build\&. The list separator is semicolon on Windows systems and colon on other systems\&.
499 \fBhard_link\fR (\fBCCACHE_HARDLINK\fR or \fBCCACHE_NOHARDLINK\fR, see Boolean values above)
501 If true, ccache will attempt to use hard links from the cache directory when creating the compiler output rather than using a file copy\&. Hard links are never made for compressed cache files\&. This means that you should not enable compression if you want to use hard links\&. The default is false\&.
507 .nr an-no-space-flag 1
514 Do not enable this option unless you are aware of the consequences\&. Using hard links may be slightly faster in some situations, but there are several pitfalls since the resulting object file will share i\-node with the cached object file:
526 If the resulting object file is modified in any way, the cached object file will be modified as well\&. For instance, if you run
527 \fBstrip object\&.o\fR
529 echo >object\&.o, you will corrupt the cache\&.
540 Programs that rely on modification times (like \(lqmake\(rq) can be confused since ccache updates the cached files\*(Aq modification times as part of the automatic cache size management\&. This will affect object files in the build tree as well, which can retrigger the linking step even though nothing really has changed\&.
544 \fBhash_dir\fR (\fBCCACHE_HASHDIR\fR or \fBCCACHE_NOHASHDIR\fR, see Boolean values above)
546 If true (which is the default), ccache will include the current working directory (CWD) in the hash that is used to distinguish two compilations when generating debug info (compiler option
548 with variations)\&. Exception: The CWD will not be included in the hash if
550 is set (and matches the CWD) and the compiler option
551 \fB\-fdebug\-prefix\-map\fR
552 is used\&. See also the discussion under
553 COMPILING IN DIFFERENT DIRECTORIES\&.
555 The reason for including the CWD in the hash by default is to prevent a problem with the storage of the current working directory in the debug info of an object file, which can lead ccache to return a cached object file that has the working directory in the debug info set incorrectly\&.
557 You can disable this setting to get cache hits when compiling the same source code in different directories if you don\(cqt mind that CWD in the debug info might be incorrect\&.
560 \fBignore_headers_in_manifest\fR (\fBCCACHE_IGNOREHEADERS\fR)
562 This setting is a list of paths to files (or directories with headers) that ccache will
564 include in the manifest list that makes up the direct mode\&. Note that this can cause stale cache hits if those headers do indeed change\&. The list separator is semicolon on Windows systems and colon on other systems\&.
567 \fBkeep_comments_cpp\fR (\fBCCACHE_COMMENTS\fR or \fBCCACHE_NOCOMMENTS\fR, see Boolean values above)
569 If true, ccache will not discard the comments before hashing preprocessor output\&. This can be used to check documentation with
570 \fB\-Wdocumentation\fR\&.
573 \fBlimit_multiple\fR (\fBCCACHE_LIMIT_MULTIPLE\fR)
575 Sets the limit when cleaning up\&. Files are deleted (in LRU order) until the levels are below the limit\&. The default is 0\&.8 (= 80%)\&. See
577 for more information\&.
580 \fBlog_file\fR (\fBCCACHE_LOGFILE\fR)
582 If set to a file path, ccache will write information on what it is doing to the specified file\&. This is useful for tracking down problems\&.
585 \fBmax_files\fR (\fBCCACHE_MAXFILES\fR)
587 This option specifies the maximum number of files to keep in the cache\&. Use 0 for no limit (which is the default)\&. See also
588 CACHE SIZE MANAGEMENT\&.
591 \fBmax_size\fR (\fBCCACHE_MAXSIZE\fR)
593 This option specifies the maximum size of the cache\&. Use 0 for no limit\&. The default value is 5G\&. Available suffixes: k, M, G, T (decimal) and Ki, Mi, Gi, Ti (binary)\&. The default suffix is G\&. See also
594 CACHE SIZE MANAGEMENT\&.
597 \fBpath\fR (\fBCCACHE_PATH\fR)
599 If set, ccache will search directories in this list when looking for the real compiler\&. The list separator is semicolon on Windows systems and colon on other systems\&. If not set, ccache will look for the first executable matching the compiler name in the normal
601 that isn\(cqt a symbolic link to ccache itself\&.
604 \fBpch_external_checksum\fR (\fBCCACHE_PCH_EXTSUM\fR or \fBCCACHE_NOPCH_EXTSUM\fR, see Boolean values above)
606 When this option is set, and ccache finds a precompiled header file, ccache will look for a file with the extension \(lq\&.sum\(rq added (e\&.g\&. \(lqpre\&.h\&.gch\&.sum\(rq), and if found, it will hash this file instead of the precompiled header itself to work around the performance penalty of hashing very large files\&.
609 \fBprefix_command\fR (\fBCCACHE_PREFIX\fR)
611 This option adds a list of prefixes (separated by space) to the command line that ccache uses when invoking the compiler\&. See also
612 USING CCACHE WITH OTHER COMPILER WRAPPERS\&.
615 \fBprefix_command_cpp\fR (\fBCCACHE_PREFIX_CPP\fR)
617 This option adds a list of prefixes (separated by space) to the command line that ccache uses when invoking the preprocessor\&.
620 \fBread_only\fR (\fBCCACHE_READONLY\fR or \fBCCACHE_NOREADONLY\fR, see Boolean values above)
622 If true, ccache will attempt to use existing cached object files, but it will not to try to add anything new to the cache\&. If you are using this because your ccache directory is read\-only, then you need to set
624 as otherwise ccache will fail to create temporary files\&.
627 \fBread_only_direct\fR (\fBCCACHE_READONLY_DIRECT\fR or \fBCCACHE_NOREADONLY_DIRECT\fR, see Boolean values above)
631 except that ccache will only try to retrieve results from the cache using the direct mode, not the preprocessor mode\&. See documentation for
633 regarding using a read\-only ccache directory\&.
636 \fBrecache\fR (\fBCCACHE_RECACHE\fR or \fBCCACHE_NORECACHE\fR, see Boolean values above)
638 If true, ccache will not use any previously stored result\&. New results will still be cached, possibly overwriting any pre\-existing results\&.
641 \fBrun_second_cpp\fR (\fBCCACHE_CPP2\fR or \fBCCACHE_NOCPP2\fR, see Boolean values above)
643 If true, ccache will first run the preprocessor to preprocess the source code (see
644 THE PREPROCESSOR MODE) and then on a cache miss run the compiler on the source code to get hold of the object file\&. This is the default\&.
646 If false, ccache will first run preprocessor to preprocess the source code and then on a cache miss run the compiler on the
647 \fIpreprocessed source code\fR
648 instead of the original source code\&. This makes cache misses slightly faster since the source code only has to be preprocessed once\&. The downside is that some compilers won\(cqt produce the same result (for instance diagnostics warnings) when compiling preprocessed source code\&.
650 A solution to the above mentioned downside is to set
653 \fB\-fdirectives\-only\fR
655 \fB\-frewrite\-includes\fR
656 (for Clang) to the compiler\&. This will cause the compiler to leave the macros and other preprocessor information, and only process the
658 directives\&. When run in this way, the preprocessor arguments will be passed to the compiler since it still has to do
660 preprocessing (like macros)\&.
663 \fBsloppiness\fR (\fBCCACHE_SLOPPINESS\fR)
665 By default, ccache tries to give as few false cache hits as possible\&. However, in certain situations it\(cqs possible that you know things that ccache can\(cqt take for granted\&. This setting makes it possible to tell ccache to relax some checks in order to increase the hit rate\&. The value should be a comma\-separated string with options\&. Available options are:
671 being present in the source\&.
674 \fBfile_stat_matches\fR
676 ccache normally examines a file\(cqs contents to determine whether it matches the cached version\&. With this option set, ccache will consider a file as matching its cached version if the mtimes and ctimes match\&.
679 \fBfile_stat_matches_ctime\fR
682 \fBfile_stat_matches\fR
683 is enabled\&. This can be useful when backdating files\*(Aq mtimes in a controlled way\&.
686 \fBinclude_file_ctime\fR
688 By default, ccache also will not cache a file if it includes a header whose ctime is too new\&. This option disables that check\&.
691 \fBinclude_file_mtime\fR
693 By default, ccache will not cache a file if it includes a header whose mtime is too new\&. This option disables that check\&.
696 \fBno_system_headers\fR
698 By default, ccache will also include all system headers in the manifest\&. With this option set, ccache will only include system headers in the hash but not add the system header files to the list of include files\&.
704 \fB#define\fRs when precompiling a header file\&. See
706 for more information\&.
715 being present in the source code\&.
718 See the discussion under
720 for more information\&.
723 \fBstats\fR (\fBCCACHE_STATS\fR or \fBCCACHE_NOSTATS\fR, see Boolean values above)
725 If true, ccache will update the statistics counters on each compilation\&. The default is true\&.
728 \fBtemporary_dir\fR (\fBCCACHE_TEMPDIR\fR)
730 This setting specifies where ccache will put temporary files\&. The default is
731 \fB<cache_dir>/tmp\fR\&.
737 .nr an-no-space-flag 1
744 In previous versions of ccache,
746 had to be on the same filesystem as the
748 path, but this requirement has been relaxed\&.)
753 \fBumask\fR (\fBCCACHE_UMASK\fR)
755 This setting specifies the umask for ccache and all child processes (such as the compiler)\&. This is mostly useful when you wish to share your cache with other users\&. Note that this also affects the file permissions set on the object files created from your compilations\&.
758 \fBunify\fR (\fBCCACHE_UNIFY\fR or \fBCCACHE_NOUNIFY\fR, see Boolean values above)
760 If true, ccache will use a C/C++ unifier when hashing the preprocessor output if the
762 option is not used\&. The unifier is slower than a normal hash, so setting this environment variable loses a little bit of speed, but it means that ccache can take advantage of not recompiling when the changes to the source code consist of reformatting only\&. Note that enabling the unifier changes the hash, so cached compilations produced when the unifier is enabled cannot be reused when the unifier is disabled, and vice versa\&. Enabling the unifier may result in incorrect line number information in compiler warning messages and expansions of the
766 .SH "CACHE SIZE MANAGEMENT"
768 By default, ccache has a 5 GB limit on the total size of files in the cache and no limit on the number of files\&. You can set different limits using the \fB\-M\fR/\fB\-\-max\-size\fR and \fB\-F\fR/\fB\-\-max\-files\fR options\&. Use \fBccache \-s/\-\-show\-stats\fR to see the cache size and the currently configured limits (in addition to other various statistics)\&.
770 Cleanup can be triggered in two different ways: automatic and manual\&.
771 .SS "Automatic cleanup"
773 ccache maintains counters for various statistics about the cache, including the size and number of all cached files\&. In order to improve performance and reduce issues with concurrent ccache invocations, there is one statistics file for each of the sixteen subdirectories in the cache\&.
775 After a new compilation result has been written to the cache, ccache will update the size and file number statistics for the subdirectory (one of sixteen) to which the result was written\&. Then, if the size counter for said subdirectory is greater than \fBmax_size / 16\fR or the file number counter is greater than \fBmax_files / 16\fR, automatic cleanup is triggered\&.
777 When automatic cleanup is triggered for a subdirectory in the cache, ccache will:
787 Count all files in the subdirectory and compute their aggregated size\&.
798 Remove files in LRU (least recently used) order until the size is at most
799 \fBlimit_multiple * max_size / 16\fR
800 and the number of files is at most
801 \fBlimit_multiple * max_files / 16\fR, where
802 \fBlimit_multiple\fR,
806 are configuration settings\&.
817 Set the size and file number counters to match the files that were kept\&.
820 The reason for removing more files than just those needed to not exceed the max limits is that a cleanup is a fairly slow operation, so it would not be a good idea to trigger it often, like after each cache miss\&.
823 You can run \fBccache \-c/\-\-cleanup\fR to force cleanup of the whole cache, i\&.e\&. all of the sixteen subdirectories\&. This will recalculate the statistics counters and make sure that the \fBmax_size\fR and \fBmax_files\fR settings are not exceeded\&. Note that \fBlimit_multiple\fR is not taken into account for manual cleanup\&.
824 .SH "CACHE COMPRESSION"
826 ccache can optionally compress all files it puts into the cache using the compression library zlib\&. While this may involve a tiny performance slowdown, it increases the number of files that fit in the cache\&. You can turn on compression with the \fBcompression\fR configuration setting and you can also tweak the compression level with \fBcompression_level\fR\&.
827 .SH "CACHE STATISTICS"
829 \fBccache \-s/\-\-show\-stats\fR can show the following statistics:
871 autoconf compile/link
874 Uncachable compilation or linking by an autoconf test\&.
878 bad compiler arguments
881 Malformed compiler argument, e\&.g\&. missing a value for an option that requires an argument or failure to read a file specified by an option argument\&.
888 A file was unexpectedly missing from the cache\&. This only happens in rare situations, e\&.g\&. if one ccache instance is about to get a file from the cache while another instance removed the file as part of cache cleanup\&.
895 A result was successfully found using the direct mode\&.
899 cache hit (preprocessed)
902 A result was successfully found using the preprocessor mode\&.
909 No result was found\&.
916 Current size of the cache\&.
923 The compiler was called for linking, not compiling\&.
927 called for preprocessing
930 The compiler was called for preprocessing, not compiling\&.
934 can\(cqt use precompiled header
937 Preconditions for using precompiled headers were not fulfilled\&.
941 ccache internal error
944 Unexpected failure, e\&.g\&. due to problems reading/writing the cache\&.
951 Number of cleanups performed, either implicitly due to the cache size limit being reached or due to explicit \fBccache \-c/\-\-cleanup\fR calls\&.
958 The compilation failed\&. No result stored in the cache\&.
962 compiler check failed
965 A compiler check program specified by \fBcompiler_check\fR (\fBCCACHE_COMPILERCHECK\fR) failed\&.
969 compiler produced empty output
972 The compiler\(cqs output file (typically an object file) was empty after compilation\&.
976 compiler produced no output
979 The compiler\(cqs output file (typically an object file) was missing after compilation\&.
983 compiler produced stdout
986 The compiler wrote data to standard output\&. This is something that compilers normally never do, so ccache is not designed to store such output in the cache\&.
990 couldn\(cqt find the compiler
993 The compiler to execute could not be found\&.
997 error hashing extra file
1000 Failure reading a file specified by \fBextra_files_to_hash\fR (\fBCCACHE_EXTRAFILES\fR)\&.
1007 Current number of files in the cache\&.
1011 multiple source files
1014 The compiler was called to compile multiple source files in one go\&. This is not supported by ccache\&.
1021 No input file was specified to the compiler\&.
1025 output to a non\-regular file
1028 The output path specified with \fB\-o\fR is not a file (e\&.g\&. a directory or a device node)\&.
1035 The compiler was instructed to write its output to standard output using \fB\-o \-\fR\&. This is not supported by ccache\&.
1042 Preprocessing the source code using the compiler\(cqs \fB\-E\fR option failed\&.
1049 When statistics were updated the last time\&.
1056 When \fBccache \-z\fR was called the last time\&.
1060 unsupported code directive
1063 Code like the assembler \fB\&.incbin\fR directive was found\&. This is not supported by ccache\&.
1067 unsupported compiler option
1070 A compiler option not supported by ccache was found\&.
1074 unsupported source language
1077 A source language e\&.g\&. specified with \fB\-x\fR was unsupported by ccache\&.
1081 .SH "HOW CCACHE WORKS"
1083 The basic idea is to detect when you are compiling exactly the same code a second time and reuse the previously produced output\&. The detection is done by hashing different kinds of information that should be unique for the compilation and then using the hash sum to identify the cached output\&. ccache uses MD4, a very fast cryptographic hash algorithm, for the hashing\&. (MD4 is nowadays too weak to be useful in cryptographic contexts, but it should be safe enough to be used to identify recompilations\&.) On a cache hit, ccache is able to supply all of the correct compiler outputs (including all warnings, dependency file, etc) from the cache\&.
1085 ccache has two ways of doing the detection:
1089 \h'-04'\(bu\h'+03'\c
1096 \fBdirect mode\fR, where ccache hashes the source code and include files directly
1101 \h'-04'\(bu\h'+03'\c
1108 \fBpreprocessor mode\fR, where ccache runs the preprocessor on the source code and hashes the result
1111 The direct mode is generally faster since running the preprocessor has some overhead\&.
1112 .SS "Common hashed information"
1114 For both modes, the following information is included in the hash:
1118 \h'-04'\(bu\h'+03'\c
1124 the extension used by the compiler for a file with preprocessor output (normally
1133 \h'-04'\(bu\h'+03'\c
1139 the compiler\(cqs size and modification time (or other compiler\-specific information specified by the
1140 \fBcompiler_check\fR
1146 \h'-04'\(bu\h'+03'\c
1152 the name of the compiler
1157 \h'-04'\(bu\h'+03'\c
1163 the current directory (if the
1170 \h'-04'\(bu\h'+03'\c
1176 contents of files specified by the
1177 \fBextra_files_to_hash\fR
1180 .SS "The direct mode"
1182 In the direct mode, the hash is formed of the common information and:
1186 \h'-04'\(bu\h'+03'\c
1192 the input source file
1197 \h'-04'\(bu\h'+03'\c
1203 the command line options
1206 Based on the hash, a data structure called \(lqmanifest\(rq is looked up in the cache\&. The manifest contains:
1210 \h'-04'\(bu\h'+03'\c
1216 references to cached compilation results (object file, dependency file, etc) that were produced by previous compilations that matched the hash
1221 \h'-04'\(bu\h'+03'\c
1227 paths to the include files that were read at the time the compilation results were stored in the cache
1232 \h'-04'\(bu\h'+03'\c
1238 hash sums of the include files at the time the compilation results were stored in the cache
1241 The current contents of the include files are then hashed and compared to the information in the manifest\&. If there is a match, ccache knows the result of the compilation\&. If there is no match, ccache falls back to running the preprocessor\&. The output from the preprocessor is parsed to find the include files that were read\&. The paths and hash sums of those include files are then stored in the manifest along with information about the produced compilation result\&.
1243 There is a catch with the direct mode: header files that were used by the compiler are recorded, but header files that were \fBnot\fR used, but would have been used if they existed, are not\&. So, when ccache checks if a result can be taken from the cache, it currently can\(cqt check if the existence of a new header file should invalidate the result\&. In practice, the direct mode is safe to use in the absolute majority of cases\&.
1245 The direct mode will be disabled if any of the following holds:
1249 \h'-04'\(bu\h'+03'\c
1255 the configuration setting
1262 \h'-04'\(bu\h'+03'\c
1268 a modification time of one of the include files is too new (needed to avoid a race condition)
1273 \h'-04'\(bu\h'+03'\c
1279 a compiler option not supported by the direct mode is used:
1283 \h'-04'\(bu\h'+03'\c
1290 \fB\-Wp,\fR\fB\fIX\fR\fR
1291 compiler option other than
1292 \fB\-Wp,\-MD,\fR\fB\fIpath\fR\fR,
1293 \fB\-Wp,\-MMD,\fR\fB\fIpath\fR\fR
1295 \fB\-Wp,\-D_define_\fR
1300 \h'-04'\(bu\h'+03'\c
1306 \fB\-Xpreprocessor\fR
1312 \h'-04'\(bu\h'+03'\c
1320 is present in the source code
1322 .SS "The preprocessor mode"
1324 In the preprocessor mode, the hash is formed of the common information and:
1328 \h'-04'\(bu\h'+03'\c
1334 the preprocessor output from running the compiler with
1340 \h'-04'\(bu\h'+03'\c
1346 the command line options except options that affect include files (\fB\-I\fR,
1348 \fB\-D\fR, etc; the theory is that these options will change the preprocessor output if they have any effect at all)
1353 \h'-04'\(bu\h'+03'\c
1359 any standard error output generated by the preprocessor
1362 Based on the hash, the cached compilation result can be looked up directly in the cache\&.
1363 .SH "CACHE DEBUGGING"
1365 To find out what information ccache actually is hashing, you can enable the debug mode via the configuration setting \fBdebug\fR or by setting \fBCCACHE_DEBUG\fR in the environment\&. This can be useful if you are investigating why you don\(cqt get cache hits\&. Note that performance will be reduced slightly\&.
1367 When the debug mode is enabled, ccache will create up to five additional files next to the object file:
1384 \fB<objectfile>\&.ccache\-input\-c\fR
1387 Binary input hashed by both the direct mode and the preprocessor mode\&.
1391 \fB<objectfile>\&.ccache\-input\-d\fR
1394 Binary input only hashed by the direct mode\&.
1398 \fB<objectfile>\&.ccache\-input\-p\fR
1401 Binary input only hashed by the preprocessor mode\&.
1405 \fB<objectfile>\&.ccache\-input\-text\fR
1408 Human\-readable combined diffable text version of the three files above\&.
1412 \fB<objectfile>\&.ccache\-log\fR
1415 Log for this object file\&.
1420 In the direct mode, ccache uses the MD4 hash of the \fBccache\-input\-c\fR + \fBccache\-input\-d\fR data (where \fB+\fR means concatenation), while the \fBccache\-input\-c\fR + \fBccache\-input\-p\fR data is used in the preprocessor mode\&.
1422 The \fBccache\-input\-text\fR file is a combined text version of the three binary input files\&. It has three sections (\(lqCOMMON\(rq, \(lqDIRECT MODE\(rq and \(lqPREPROCESSOR MODE\(rq), which is turn contain annotations that say what kind of data comes next\&.
1424 To debug why you don\(cqt get an expected cache hit for an object file, you can do something like this:
1434 Build with debug mode enabled\&.
1446 \fB<objectfile>\&.ccache\-*\fR
1458 Build again with debug mode enabled\&.
1470 \fB<objectfile>\&.ccache\-input\-text\fR
1471 for the two builds\&. This together with the
1472 \fB<objectfile>\&.ccache\-log\fR
1473 files should give you some clues about what is happening\&.
1475 .SH "COMPILING IN DIFFERENT DIRECTORIES"
1477 Some information included in the hash that identifies a unique compilation can contain absolute paths:
1481 \h'-04'\(bu\h'+03'\c
1487 The preprocessed source code may contain absolute paths to include files if the compiler option
1489 is used or if absolute paths are given to
1491 and similar compiler options\&.
1496 \h'-04'\(bu\h'+03'\c
1502 Paths specified by compiler options (such as
1504 \fB\-MF\fR, etc) on the command line may be absolute\&.
1509 \h'-04'\(bu\h'+03'\c
1515 The source code file path may be absolute, and that path may substituted for
1517 macros in the source code or included in warnings emitted to standard error by the preprocessor\&.
1520 This means that if you compile the same code in different locations, you can\(cqt share compilation results between the different build directories since you get cache misses because of the absolute build directory paths that are part of the hash\&.
1522 Here\(cqs what can be done to enable cache hits between different build directories:
1526 \h'-04'\(bu\h'+03'\c
1534 (or similar) to add debug information to the object file, you must either:
1538 \h'-04'\(bu\h'+03'\c
1545 \fB\-fdebug\-prefix\-map=\fR\fB\fIold\fR\fR\fB=\fR\fB\fInew\fR\fR
1546 option for relocating debug info to a common prefix (e\&.g\&.
1547 \fB\-fdebug\-prefix\-map=$PWD=\&.\fR); or
1552 \h'-04'\(bu\h'+03'\c
1559 \fBhash_dir = false\fR\&.
1565 \h'-04'\(bu\h'+03'\c
1571 If you use absolute paths anywhere on the command line (e\&.g\&. the source code file path or an argument to compiler options like
1574 \fB\-MF\fR), you must to set
1576 to an absolute path to a \(lqbase directory\(rq\&. ccache will then rewrite absolute paths under that directory to relative before computing the hash\&.
1578 .SH "PRECOMPILED HEADERS"
1580 ccache has support for GCC\(cqs precompiled headers\&. However, you have to do some things to make it work properly:
1584 \h'-04'\(bu\h'+03'\c
1593 \fBpch_defines,time_macros\fR\&. The reason is that ccache can\(cqt tell whether
1597 is used when using a precompiled header\&. Further, it can\(cqt detect changes in
1598 \fB#define\fRs in the source code because of how preprocessing works in combination with precompiled headers\&.
1603 \h'-04'\(bu\h'+03'\c
1613 \h'-04'\(bu\h'+03'\c
1621 compiler option to include the precompiled header (i\&.e\&., don\(cqt use
1623 in the source code to include the header); or
1628 \h'-04'\(bu\h'+03'\c
1634 (for the Clang compiler) use the
1635 \fB\-include\-pch\fR
1636 compiler option to include the PCH file generated from the precompiled header; or
1641 \h'-04'\(bu\h'+03'\c
1648 \fB\-fpch\-preprocess\fR
1649 compiler option when compiling\&.
1652 If you don\(cqt do this, either the non\-precompiled version of the header file will be used (if available) or ccache will fall back to running the real compiler and increase the statistics counter \(lqpreprocessor error\(rq (if the non\-precompiled header file is not available)\&.
1654 .SH "SHARING A CACHE"
1656 A group of developers can increase the cache hit rate by sharing a cache directory\&. To share a cache without unpleasant side effects, the following conditions should to be met:
1660 \h'-04'\(bu\h'+03'\c
1666 Use the same cache directory\&.
1671 \h'-04'\(bu\h'+03'\c
1677 Make sure that the configuration setting
1679 is false (which is the default)\&.
1684 \h'-04'\(bu\h'+03'\c
1690 Make sure that all users are in the same group\&.
1695 \h'-04'\(bu\h'+03'\c
1701 Set the configuration setting
1703 to 002\&. This ensures that cached files are accessible to everyone in the group\&.
1708 \h'-04'\(bu\h'+03'\c
1714 Make sure that all users have write permission in the entire cache directory (and that you trust all users of the shared cache)\&.
1719 \h'-04'\(bu\h'+03'\c
1725 Make sure that the setgid bit is set on all directories in the cache\&. This tells the filesystem to inherit group ownership for new directories\&. The following command might be useful for this:
1731 find $CCACHE_DIR \-type d | xargs chmod g+s
1738 The reason to avoid the hard link mode is that the hard links cause unwanted side effects, as all links to a cached file share the file\(cqs modification timestamp\&. This results in false dependencies to be triggered by timestamp\-based build systems whenever another user links to an existing file\&. Typically, users will see that their libraries and binaries are relinked without reason\&.
1740 You may also want to make sure that a base directory is set appropriately, as discussed in a previous section\&.
1741 .SH "SHARING A CACHE ON NFS"
1743 It is possible to put the cache directory on an NFS filesystem (or similar filesystems), but keep in mind that:
1747 \h'-04'\(bu\h'+03'\c
1753 Having the cache on NFS may slow down compilation\&. Make sure to do some benchmarking to see if it\(cqs worth it\&.
1758 \h'-04'\(bu\h'+03'\c
1764 ccache hasn\(cqt been tested very thoroughly on NFS\&.
1767 A tip is to set \fBtemporary_dir\fR to a directory on the local host to avoid NFS traffic for temporary files\&.
1768 .SH "USING CCACHE WITH OTHER COMPILER WRAPPERS"
1770 The recommended way of combining ccache with another compiler wrapper (such as \(lqdistcc\(rq) is by letting ccache execute the compiler wrapper\&. This is accomplished by defining the configuration setting \fBprefix_command\fR, for example by setting the environment variable \fBCCACHE_PREFIX\fR to the name of the wrapper (e\&.g\&. \fBdistcc\fR)\&. ccache will then prefix the command line with the specified command when running the compiler\&. To specify several prefix commands, set \fBprefix_command\fR to a colon\-separated list of commands\&.
1772 Unless you set \fBcompiler_check\fR to a suitable command (see the description of that configuration option), it is not recommended to use the form \fBccache anotherwrapper compiler args\fR as the compilation command\&. It\(cqs also not recommended to use the masquerading technique for the other compiler wrapper\&. The reason is that by default, ccache will in both cases hash the mtime and size of the other wrapper instead of the real compiler, which means that:
1776 \h'-04'\(bu\h'+03'\c
1782 Compiler upgrades will not be detected properly\&.
1787 \h'-04'\(bu\h'+03'\c
1793 The cached results will not be shared between compilations with and without the other wrapper\&.
1796 Another minor thing is that if \fBprefix_command\fR is used, ccache will not invoke the other wrapper when running the preprocessor, which increases performance\&. You can use the \fBprefix_command_cpp\fR configuration setting if you also want to invoke the other wrapper when doing preprocessing (normally by adding \fB\-E\fR)\&.
1801 \h'-04'\(bu\h'+03'\c
1807 The direct mode fails to pick up new header files in some rare scenarios\&. See
1814 \h'-04'\(bu\h'+03'\c
1820 When run via ccache, warning messages produced by GCC 4\&.9 and newer will only be colored when the environment variable
1822 is set\&. An alternative to setting
1825 \fB\-fdiagnostics\-color\fR
1826 explicitly when compiling (but then color codes will also be present when redirecting stderr to a file)\&.
1831 \h'-04'\(bu\h'+03'\c
1837 If ccache guesses that the compiler may emit colored warnings, then a compilation with stderr referring to a TTY will be considered different from a compilation with a redirected stderr, thus not sharing cache entries\&. This happens for clang by default and for GCC when
1839 is set as mentioned above\&. If you want to share cache hits, you can pass
1840 \fB\-f[no\-]diagnostics\-color\fR
1842 \fB\-f[no\-]color\-diagnostics\fR
1843 (clang) explicitly when compiling (but then color codes will be either on or off for both the TTY and the redirected case)\&.
1845 .SH "TROUBLESHOOTING"
1848 A general tip for getting information about what ccache is doing is to enable debug logging by setting \fBlog_file\fR\&. The log contains executed commands, important decisions that ccache makes, read and written files, etc\&. Another way of keeping track of what is happening is to check the output of \fBccache \-s\fR\&.
1851 ccache has been written to perform well out of the box, but sometimes you may have to do some adjustments of how you use the compiler and ccache in order to improve performance\&.
1853 Since ccache works best when I/O is fast, put the cache directory on a fast storage device if possible\&. Having lots of free memory so that files in the cache directory stay in the disk cache is also preferable\&.
1855 A good way of monitoring how well ccache works is to run \fBccache \-s\fR before and after your build and then compare the statistics counters\&. Here are some common problems and what may be done to increase the hit rate:
1859 \h'-04'\(bu\h'+03'\c
1865 If \(lqcache hit (preprocessed)\(rq has been incremented instead of \(lqcache hit (direct)\(rq, ccache has fallen back to preprocessor mode, which is generally slower\&. Some possible reasons are:
1869 \h'-04'\(bu\h'+03'\c
1875 The source code has been modified in such a way that the preprocessor output is not affected\&.
1880 \h'-04'\(bu\h'+03'\c
1886 Compiler arguments that are hashed in the direct mode but not in the preprocessor mode have changed (\fB\-I\fR,
1888 \fB\-D\fR, etc) and they didn\(cqt affect the preprocessor output\&.
1893 \h'-04'\(bu\h'+03'\c
1900 \fB\-Xpreprocessor\fR
1902 \fB\-Wp,\fR\fB\fIX\fR\fR
1904 \fB\-Wp,\-MD,\fR\fB\fIpath\fR\fR,
1905 \fB\-Wp,\-MMD,\fR\fB\fIpath\fR\fR, and
1906 \fB\-Wp,\-D_define_\fR) is used\&.
1911 \h'-04'\(bu\h'+03'\c
1917 This was the first compilation with a new value of the base directory setting\&.
1922 \h'-04'\(bu\h'+03'\c
1928 A modification time of one of the include files is too new (created the same second as the compilation is being done)\&. This check is made to avoid a race condition\&. To fix this, create the include file earlier in the build process, if possible, or set
1931 \fBinclude_file_mtime\fR
1932 if you are willing to take the risk\&. (The race condition consists of these events: the preprocessor is run; an include file is modified by someone; the new include file is hashed by ccache; the real compiler is run on the preprocessor\(cqs output, which contains data from the old header file; the wrong object file is stored in the cache\&.)
1937 \h'-04'\(bu\h'+03'\c
1945 preprocessor macro is (potentially) being used\&. ccache turns off direct mode if
1947 is present in the source code\&. This is done as a safety measure since the string indicates that a
1951 affect the output\&. (To be sure, ccache would have to run the preprocessor, but the sole point of the direct mode is to avoid that\&.) If you know that
1953 isn\(cqt used in practise, or don\(cqt care if ccache produces objects where
1955 is expanded to something in the past, you can set
1958 \fBtime_macros\fR\&.
1963 \h'-04'\(bu\h'+03'\c
1971 preprocessor macro is (potentially) being used and the date has changed\&. This is similar to how
1975 is present in the source code, ccache hashes the current date in order to be able to produce the correct object file if the
1977 macro affects the output\&. If you know that
1979 isn\(cqt used in practise, or don\(cqt care if ccache produces objects where
1981 is expanded to something in the past, you can set
1984 \fBtime_macros\fR\&.
1989 \h'-04'\(bu\h'+03'\c
1997 preprocessor macro is (potentially) being used and the file path has changed\&. If
1999 is present in the source code, ccache hashes the current input file path in order to be able to produce the correct object file if the
2001 macro affects the output\&. If you know that
2003 isn\(cqt used in practise, or don\(cqt care if ccache produces objects where
2005 is expanded to the wrong path, you can set
2014 \h'-04'\(bu\h'+03'\c
2020 If \(lqcache miss\(rq has been incremented even though the same code has been compiled and cached before, ccache has either detected that something has changed anyway or a cleanup has been performed (either explicitly or implicitly when a cache limit has been reached)\&. Some perhaps unobvious things that may result in a cache miss are usage of
2024 macros, or use of automatically generated code that contains a timestamp, build counter or other volatile information\&.
2029 \h'-04'\(bu\h'+03'\c
2035 If \(lqmultiple source files\(rq has been incremented, it\(cqs an indication that the compiler has been invoked on several source code files at once\&. ccache doesn\(cqt support that\&. Compile the source code files separately if possible\&.
2040 \h'-04'\(bu\h'+03'\c
2046 If \(lqunsupported compiler option\(rq has been incremented, enable debug logging and check which option was rejected\&.
2051 \h'-04'\(bu\h'+03'\c
2057 If \(lqpreprocessor error\(rq has been incremented, one possible reason is that precompiled headers are being used\&. See
2059 for how to remedy this\&.
2064 \h'-04'\(bu\h'+03'\c
2070 If \(lqcan\(cqt use precompiled header\(rq has been incremented, see
2071 PRECOMPILED HEADERS\&.
2073 .SS "Corrupt object files"
2075 It should be noted that ccache is susceptible to general storage problems\&. If a bad object file sneaks into the cache for some reason, it will of course stay bad\&. Some possible reasons for erroneous object files are bad hardware (disk drive, disk controller, memory, etc), buggy drivers or file systems, a bad \fBprefix_command\fR or compiler wrapper\&. If this happens, the easiest way of fixing it is this:
2085 Build so that the bad object file ends up in the build tree\&.
2096 Remove the bad object file from the build tree\&.
2108 \fBCCACHE_RECACHE\fR
2112 An alternative is to clear the whole cache with \fBccache \-C\fR if you don\(cqt mind losing other cached results\&.
2114 There are no reported issues about ccache producing broken object files reproducibly\&. That doesn\(cqt mean it can\(cqt happen, so if you find a repeatable case, please report it\&.
2115 .SH "MORE INFORMATION"
2117 Credits, mailing list information, bug reporting instructions, source code, etc, can be found on ccache\(cqs web site: https://ccache\&.samba\&.org\&.
2120 ccache was originally written by Andrew Tridgell and is currently developed and maintained by Joel Rosdahl\&. See AUTHORS\&.txt or AUTHORS\&.html and https://ccache\&.samba\&.org/credits\&.html for a list of contributors\&.
projects / platform / upstream / ccache.git / blob