Ccache version 4.9.1 is now available. Release archives can be found here:
https://ccache.dev/download.html
Release notes:
https://ccache.dev/releasenotes.html#_ccache_4_9_1
-- Joel
___
ccache mailing list
ccache@lists.samba.org
Ccache version 4.9 is now available. Release archives can be found here:
https://ccache.dev/download.html
Release notes:
https://ccache.dev/releasenotes.html#_ccache_4_9
-- Joel
___
ccache mailing list
ccache@lists.samba.org
Hi Stefan,
On Tue, Sep 19, 2023, at 20:27, Stefan Constantin via ccache wrote:
> I would like to contribute some time/code to ccache if there are areas
> where help is needed.
Nice!
> For example some time ago I added the smallest of features (expanding an
> env var in ccache's config) and the
Ccache version 4.8.3 is now available. Release archives can be found here:
https://ccache.dev/download.html
Release notes:
https://ccache.dev/releasenotes.html#_ccache_4_8_3
-- Joel
___
ccache mailing list
ccache@lists.samba.org
Ccache version 4.8.2 is now available. Release archives can be found here:
https://ccache.dev/download.html
Release notes:
https://ccache.dev/releasenotes.html#_ccache_4_8_2
-- Joel
___
ccache mailing list
ccache@lists.samba.org
Ccache version 4.8.1 is now available. Release archives can be found here:
https://ccache.dev/download.html
Release notes:
https://ccache.dev/releasenotes.html#_ccache_4_8_1
-- Joel
___
ccache mailing list
ccache@lists.samba.org
Ccache version 4.8 is now available. Release archives can be found here:
https://ccache.dev/download.html
Release notes:
https://ccache.dev/releasenotes.html#_ccache_4_8
-- Joel
___
ccache mailing list
ccache@lists.samba.org
Ccache version 4.7.4 is now available. Release archives can be found here:
https://ccache.dev/download.html
Release notes:
https://ccache.dev/releasenotes.html#_ccache_4_7_4
-- Joel
___
ccache mailing list
ccache@lists.samba.org
Ccache version 4.7.3 is now available. Release archives can be found here:
https://ccache.dev/download.html
Release notes:
https://ccache.dev/releasenotes.html#_ccache_4_7_3
-- Joel
___
ccache mailing list
ccache@lists.samba.org
Ccache version 4.7.2 is now available. Release archives can be found here:
https://ccache.dev/download.html
Release notes:
https://ccache.dev/releasenotes.html#_ccache_4_7_2
-- Joel
___
ccache mailing list
ccache@lists.samba.org
Ccache version 4.7.1 is now available. Release archives can be found here:
https://ccache.dev/download.html
Release notes:
https://ccache.dev/releasenotes.html#_ccache_4_7_1
-- Joel
___
ccache mailing list
ccache@lists.samba.org
Ccache version 4.7 is now available. Release archives can be found here:
https://ccache.dev/download.html
Release notes:
https://ccache.dev/releasenotes.html#_ccache_4_7
-- Joel
___
ccache mailing list
ccache@lists.samba.org
Ccache version 4.6.3 is now available. Release archives can be found here:
https://ccache.dev/download.html
Release notes:
https://ccache.dev/releasenotes.html#_ccache_4_6_3
-- Joel
___
ccache mailing list
ccache@lists.samba.org
Ccache version 4.6.2 is now available. Release archives can be found here:
https://ccache.dev/download.html
Release notes:
https://ccache.dev/releasenotes.html#_ccache_4_6_2
-- Joel
___
ccache mailing list
ccache@lists.samba.org
Ccache version 4.6.1 is now available. Release archives can be found here:
https://ccache.dev/download.html
Release notes:
https://ccache.dev/releasenotes.html#_ccache_4_6_1
-- Joel
___
ccache mailing list
ccache@lists.samba.org
Aleksey Midenkov wrote:
> After the software upgrade I noticed my IDE cannot compile a project
> after it was built from the terminal. It turned out that build
> directory now contains objects with such strange permissions:
>
> -r--r--r--
>
> When I removed ccache from the compiling command it
Ccache version 4.6 is now available. Release archives can be found here:
https://ccache.dev/download.html
Release notes:
https://ccache.dev/releasenotes.html#_ccache_4_6
-- Joel
___
ccache mailing list
ccache@lists.samba.org
Ccache version 4.5.1 is now available. Release archives can be found here:
https://ccache.dev/download.html
Bug fixes:
- Fixed entry_size field for result entries. This bug affected the
recompression feature (“-X”/“--recompress”) in ccache 4.5.
- The actual compression level is now
Ccache version 4.5 is now available. Release archives can be found here:
https://ccache.dev/download.html
New features:
- Made various improvements to the cache entry format. Among other things,
the header now contains a creation timestamp and a note of the ccache
version used to
On Tue, 12 Oct 2021 at 18:35, Sebert, Holger.ext via ccache
wrote:
> I would like to upgrade Ccache from version 3.4.1 to 4.2 (or newer).
>
> Are the caches from the old version still valid or should I clean them up
> before upgrading?
The cached results from the old version will not be used by
Ccache version 4.4.2 is now available. Release archives can be found here:
https://ccache.dev/download.html
Bug fixes:
- Fixed a bug introduced in 4.4 where ccache could produce false direct cache
hits in some situations if it decides to disable the direct mode
temporarily (e.g.
Ccache version 4.4.1 is now available. Release archives can be found here:
https://ccache.dev/download.html
New features:
- The secondary storage statistics section of “-s/--show-stats” is now shown
only if it's non-empty or with two verbose options.
- Added display of statistics
Ccache version 4.3 is now available. Release archives can be found here:
https://ccache.dev/download.html
New features:
- Ccache now ignores the Clang compiler option “-ivfsoverlay” and its
argument if you opt in to “ivfsoverlay sloppiness”. This is useful if you
use Xcode, which
On Sun, 18 Apr 2021 at 10:04, R. Diez via ccache wrote:
> First of all, I have been using ccache for years. Many thanks for this great
> tool.
You're welcome.
> I have come to the conclusion that these particular pauses are due to ccache
> automatically pruning its cache.
I haven't really
Ccache version 4.2.1 is now available. Release archives can be found here:
https://ccache.dev/download.html
Bug fixes:
- Ccache now only “dup2”s stderr into “$UNCACHED_ERR_FD” for calls to the
preprocessor/compiler. This works around a complex bug in interaction with
GNU Make, LTO
On Sun, 7 Feb 2021 at 12:26, Sam Varshavchik via ccache
wrote:
> I've been chasing down non-deterministic, random build fails.
Thanks for the thorough investigation!
> So, now what? Both ccache, and the linker are contributing to this situation.
> ccache leaks the file descriptor (to distcc
Ccache version 4.2 is now available. Release archives can be found here:
https://ccache.dev/download.html
New features:
- Improved calculation of relative paths when using “base_dir” to also
consider canonical paths (i.e. paths with dereferenced symlinks) as
candidates.
- Added
On Mon, 7 Dec 2020 at 22:55, Steffen Dettmer via ccache
wrote:
> I just tested with ccache 3.7.12 and "ccache -s" that it seems to work as I
> expect
Cool, my memory was wrong about this! Or alternatively, it might be that the
final implementation of the config file handling did not become what
On Thu, 3 Dec 2020 at 11:28, Steffen Dettmer wrote:
> Is upgrading to ccache 4 a "drop-in replacement" even if sharing the cache
> directory with still running ccache 3 versions?
> [...]
> Does it really make new versions a "plug-in replacement"?
> [...]
> So in short: I would not need to change
Ccache version 4.1 is now available. Release archives can be found here:
https://ccache.dev/download.html
New features:
- Symlinks are now followed when guessing the compiler. This makes ccache
able to guess compiler type “GCC” for a common symlink chain like this:
“/usr/bin/cc” →
Ccache version 4.0 is now available. Release archives can be found here:
https://ccache.dev/download.html
Summary of major changes:
- Changed the default cache directory location to follow the XDG base
directory specification.
- Changed compression algorithm from Deflate (zlib) to
ccache version 3.7.12 is now available. Release archives can be found here:
https://ccache.dev/download.html
Bug fixes:
- Coverage files (“.gcno”) produced by GCC 9+ when using “-fprofile-dir=dir”
are now handled gracefully by falling back to running the compiler.
- Fixed writing
Hi Vijay,
On Fri, 28 Aug 2020 at 13:17, Vijay Tandeker wrote:
> Every night I do the compilation. I don't know but whenever I do the
> compilation, cache size increases by few GBs (sometimes by few MBs).
That sounds perfectly normal for a build that generates parts of its source
code with
On Mon, 17 Aug 2020 at 15:34, Christian Ledergerber
wrote:
> [...] The point is: I think this is not a coner-case, but people use this
> configuration abundantly.
I just wanted to stress the point that tools need to handle all configurations
correctly, regardless of whether they are popular or
On Fri, 14 Aug 2020 at 08:39, Christian Ledergerber
wrote:
>
> I have created the following issue for cmake to launch the discussion:
> https://gitlab.kitware.com/cmake/cmake/-/issues/21092
When you described your idea I didn't think you meant making changes
for incorporation in the upstream
On Sun, 2 Aug 2020 at 19:49, Christian Ledergerber via ccache
wrote:
> In the mean-time I have been thinking some more and what I am afraid of
> is that the result will not be correct if the flags to clang-tidy change.
>
> A typical command run by make looks like this:
>
> cd
On Sun, 2 Aug 2020 at 18:55, Christian Ledergerber via ccache
wrote:
> [...]
> To me it seems like the following should work:
>
> 1. try to use ccache
>
> 2. if no hit:
>
> - run clang-tidy
>
> - run clang
>
> For this I would need to know whether ccache generated a hit - lets say
> as return
ccache version 3.7.11 is now available. Release archives can be found here:
https://ccache.dev/download.html
Bug fixes:
- Added knowledge about “-fprofile-{correction,reorder-functions,values}”.
- ccache now handles the Intel compiler option “-xCODE” (where “CODE” is a
processor
ccache version 3.7.10 is now available. Release archives can be found here:
https://ccache.dev/download.html
Bug fixes:
- Improved handling of profiling options. ccache should now work correctly
for profiling options like “-fprofile-{generate,use}[=path]” for GCC ≥ 9
and Clang as
ccache version 3.7.9 is now available. Release archives can be found here:
https://ccache.dev/download.html
Bug fixes:
- Fixed replacing of /dev/null when building as root with hard link mode
enabled and using “-o /dev/null”.
- Removed incorrect assertion resulting in “ccache:
On Mon, 23 Mar 2020 at 17:11, Steffen Dettmer via ccache
wrote:
> Just BTW, isn't it common to build in some $builddir different from top
> $srcdir (e.g. automake, cmake) and in that case couldn't the common case need
> two base directories?
Note that base_dir doesn't have to be the top source
On Tue, 17 Mar 2020 at 10:06, Steffen Dettmer via ccache
wrote:
> As workaround for a special unrelated issue currently we redefine
> __FILE__ (and try to remove that redefinition). I understand that
> ccache still works thanks to CCACHE_BASEDIR even for __FILE__ usage
> inside files. Is that
ccache version 3.7.8 is now available. Release archives are
available here:
https://ccache.dev/download.html
Note: There are now 32 and 64 bit Windows binary releases available as well.
Bug fixes:
- Use “$PWD” instead of the real CWD (current working directory) when
checking for CWD
ccache version 3.7.7 is now available.
Source archives:
https://github.com/ccache/ccache/releases/download/v3.7.7/ccache-3.7.7.tar.gz
https://github.com/ccache/ccache/releases/download/v3.7.7/ccache-3.7.7.tar.xz
The source archives have been signed with my OpenPGP key (ID 5594ADB8,
Source archives:
https://github.com/ccache/ccache/releases/download/v3.7.6/ccache-3.7.6.tar.gz
https://github.com/ccache/ccache/releases/download/v3.7.6/ccache-3.7.6.tar.xz
The source archives have been signed with my OpenPGP key (ID 5594ADB8,
fingerprint 5A93 9A71 A467 92CF 5786 6A51
ccache version 3.7.5 is now available.
Source archives:
https://github.com/ccache/ccache/releases/download/v3.7.5/ccache-3.7.5.tar.gz
https://github.com/ccache/ccache/releases/download/v3.7.5/ccache-3.7.5.tar.xz
The source archives have been signed with my OpenPGP key (ID 5594ADB8,
ccache version 3.7.4 is now available.
Source archives:
https://github.com/ccache/ccache/releases/download/v3.7.4/ccache-3.7.4.tar.gz
https://github.com/ccache/ccache/releases/download/v3.7.4/ccache-3.7.4.tar.xz
The source archives have been signed with my OpenPGP key (ID 5594ADB8,
ccache version 3.7.3 is now available.
Source archives:
https://github.com/ccache/ccache/releases/download/v3.7.3/ccache-3.7.3.tar.gz
https://github.com/ccache/ccache/releases/download/v3.7.3/ccache-3.7.3.tar.xz
The source archives have been signed with my OpenPGP key (ID 5594ADB8,
ccache version 3.7.2 is now available.
Source archives:
https://github.com/ccache/ccache/releases/download/v3.7.2/ccache-3.7.2.tar.gz
https://github.com/ccache/ccache/releases/download/v3.7.2/ccache-3.7.2.tar.xz
The source archives have been signed with my OpenPGP key (ID 5594ADB8,
On Tue, 25 Jun 2019 at 00:28, Malfettone, Kris via ccache
wrote:
> So what I seem to be observing is only when I do a ninja -t clean or make
> clean. This removes all of my generated files (.h and .cpp files) and of
> course the normal build outputs. A subsequent run is then mostly cache
>
Hi Kris,
On Fri, 21 Jun 2019 at 02:43, Malfettone, Kris wrote:
> My project uses a large number of generated C++ files (.h/.cpp files). On a
> clean build these files are cleaned up as well. As a result during the next
> build since they are generated again they will all have a newer mtime and
>
Hi Henri,
Verifying the value sounds like a good improvement.
The fix you suggested doesn't quite work since there is no conf variable
available, so I guess you have made other changes as well. Also, there is
an optional "verifier" for some configuration items that should be run as
well. I made
Hi Francios,
On Tue, 7 May 2019 at 12:17, Francois E via ccache
wrote:
> We use a shared ccache server hosted on a remote server, some of us
> experience slow connection to that server. I was wondering if
> compression would help in this case, i.e does the (un)compression occur
> at the server
On Wed, 10 Apr 2019 at 17:46, 林博仁 via ccache wrote:
> I've [...] built a working snap [of ccache]
Cool, thanks for the notice.
> I'm also looking forward to working with you to make the packaging
> work upstream (if you're interested).
I'm happy if you would like to continue maintaining the
ccache version 3.7.1 is now available.
Source archives:
https://github.com/ccache/ccache/releases/download/v3.7.1/ccache-3.7.1.tar.bz2
https://github.com/ccache/ccache/releases/download/v3.7.1/ccache-3.7.1.tar.gz
ccache version 3.7 is now available.
Details may be read in the release notes:
http://ccache.dev/releasenotes.html#_ccache_3_7
Source archives are available here:
https://github.com/ccache/ccache/releases/download/v3.7/ccache-3.7.tar.bz2
[The previous mail contained changelog entries for ccache 3.6. Sorry
about that, I've rewritten my scripts for doing releases and this one
slipped through.]
ccache version 3.7 is now available.
Source archives:
https://github.com/ccache/ccache/releases/download/v3.7/ccache-3.7.tar.bz2
On Tue, 5 Mar 2019 at 08:08, Haio Maio via ccache
wrote:
> On February 22, 2019 at 8:42 PM Joel Rosdahl wrote:
>
> > Before trying to set up icecc as a wrapper together with ccache, you need
> > to make sure that ccache is used by the command(s) that you abbreviated as
> > "compile".
> >
> >
On Fri, 22 Feb 2019 at 19:42, Haio Maio via ccache
wrote:
> Im afraid, I didnt understand your question?
>
> Im trying to use icecc/icecream as a wrapper for the compiler. Could you be
> more specific of what did you mean?
Before trying to set up icecc as a wrapper together with ccache, you
On Wed, 20 Feb 2019 at 12:46, Haio Maio via ccache
wrote:
> Any suggestion of how to use successfully icecc with ccache? The following
> doesnt work ...
>
> export CCACHE_PREFIX=icecc
>
> compile
>
> ccache -s
> [...]
It looks like ccache is never called in the compile step, so you need to make
On Tue, 22 Jan 2019 at 10:36, Robert Yang via ccache
wrote:
> Fixed:
> $ export CCACHE_DEBUG=1
> $ ccache gcc -c hello.c -o /dev/null
>
> Segmentation fault (core dumped)
>
> This is because failed to open /dev/null.foo (Permission denied), check file
> stream before write to it can fix the
On Tue, 22 Jan 2019 at 10:36, Robert Yang via ccache
wrote:
> The all_cppflags changes path to filename which causes file name too long
> error when the path is longer than NAME_MAX (usually 255). Strip srcdir
> to fix the problem.
Thanks, applied on master.
-- Joel
ccache version 3.6 is now available.
Details may be read in the release notes:
http://ccache.samba.org/releasenotes.html#_ccache_3_6
Source archives are available here:
https://www.samba.org/ftp/ccache/ccache-3.6.tar.bz2
https://www.samba.org/ftp/ccache/ccache-3.6.tar.gz
On Thu, 3 Jan 2019 at 23:02, Andre Calfa wrote:
> One of the motivations is that our current compiler cache is only supported
> locally for each build server. In some cases the compilation of a single
> input file takes a long time due to its size, and we cannot avoid its
> compilation when the
Hi Andre,
On Thu, 3 Jan 2019 at 20:39, Andre Calfa via ccache
wrote:
> We currently have our own compiler cache for the compiler we developed, but
> we would like to switch to ccache if possible. Our compiler takes as input
> a custom language and generates both a .cpp file and a .h file. I
The ccache 3.5.1 release archives announced yesterday unfortunately
included an incorrectly generated configure script, so they have been
pulled.
Fixed source archives are available here:
https://www.samba.org/ftp/ccache/ccache-3.5.1a.tar.bz2
ccache version 3.5.1 is now available.
Details may be read in the release notes:
http://ccache.samba.org/releasenotes.html#_ccache_3_5_1
Source archives are available here:
https://www.samba.org/ftp/ccache/ccache-3.5.1.tar.bz2
https://www.samba.org/ftp/ccache/ccache-3.5.1.tar.gz
Hi,
On Sat, 22 Dec 2018 at 04:25, swedebugia--- via ccache
wrote:
> The site-ccache of guile does not support partials of files and every
> update to our scheme-files.
What is "site-ccache"? After reading
https://www.gnu.org/software/guile/manual/html_node/Build-Config.html, it does
not sound
On Fri, 16 Nov 2018 at 19:46, Nico Huber via ccache
wrote:
> [...]
> If I'm looking at the right spot in the code, I can see that 1. happens
> on purpose (in process_preprocessed_file(), ccache.c:945). Though, I
> wonder why?
The history of that code is that
ccache version 3.5 is now available.
Details may be read in the release notes:
http://ccache.samba.org/releasenotes.html#_ccache_3_5
Source archives are available here:
https://www.samba.org/ftp/ccache/ccache-3.5.tar.bz2
https://www.samba.org/ftp/ccache/ccache-3.5.tar.gz
ccache version 3.4.3 is now available.
Details may be read in the release notes:
http://ccache.samba.org/releasenotes.html#_ccache_3_4_3
Source archives are available here:
https://www.samba.org/ftp/ccache/ccache-3.4.3.tar.bz2
https://www.samba.org/ftp/ccache/ccache-3.4.3.tar.gz
ccache version 3.4.2 is now available.
Details may be read in the release notes:
http://ccache.samba.org/releasenotes.html#_ccache_3_4_2
Source archives are available here:
https://www.samba.org/ftp/ccache/ccache-3.4.2.tar.bz2
https://www.samba.org/ftp/ccache/ccache-3.4.2.tar.gz
On 16 March 2018 at 12:52, Forte, Greg via ccache
wrote:
> Tried this with and without CCACHE_DIR set and exported - with it, I see the
> same output you showed, including the unset, and the test still fails: [...]
OK.
What's common between the two tests that fail for
ccache version 3.4.1 is now available.
Details may be read in the release notes:
http://ccache.samba.org/releasenotes.html#_ccache_3_4_1
Source archives are available here:
https://www.samba.org/ftp/ccache/ccache-3.4.1.tar.bz2
https://www.samba.org/ftp/ccache/ccache-3.4.1.tar.gz
ccache version 3.4 is now available.
Details may be read in the release notes:
http://ccache.samba.org/releasenotes.html#_ccache_3_4
Source archives are available here:
https://www.samba.org/ftp/ccache/ccache-3.4.tar.bz2
https://www.samba.org/ftp/ccache/ccache-3.4.tar.gz
On 29 January 2018 at 07:14, Scott Bennett wrote:
> Countless data base software implementations handle these situations
> acceptably well.
Sigh.
I see. You're talking about a completely different model than what
ccache currently uses, which was not clear to me when I read
ccache version 3.3.6 is now available.
Details may be read in the release notes:
http://ccache.samba.org/releasenotes.html#_ccache_3_3_6
Source archives are available here:
https://www.samba.org/ftp/ccache/ccache-3.3.6.tar.bz2
https://www.samba.org/ftp/ccache/ccache-3.3.6.tar.gz
On 7 January 2018 at 14:02, Scott Bennett wrote:
> The design problem is that there is no centralized index maintained of
> cache entries' paths, their sizes, and their timestamps, necessitating
> the plumbing of the directory trees. [...]
Thanks for sharing your ideas!
I fully agree that the
On 14 January 2018 at 12:01, Michael Bazzinotti via ccache
wrote:
> My ccache was separate for both my root user and main user account. Now, I
> have a shared ccache pointing to the main user's cache.
> How can I merge the root and user ccache directories?
Try something
ccache version 3.3.5 is now available.
Details may be read in the release notes:
http://ccache.samba.org/releasenotes.html#_ccache_3_3_5
Source archives are available here:
https://www.samba.org/ftp/ccache/ccache-3.3.5.tar.bz2
https://www.samba.org/ftp/ccache/ccache-3.3.5.tar.gz
On 23 December 2017 at 14:49, Radu Rendec via ccache wrote:
> I ran across a weird issue where test.sh fails in the CCACHE_NOHASHDIR
> test because the CCACHE_HASHDIR variable happens to be set in my
> environment.
[...]
My idea is to iterate through the output of
Hi Scott,
On 19 December 2017 at 02:16, Scott Bennett via ccache <
ccache@lists.samba.org> wrote:
> I set "limit_multiple = 0.95" in ccache.conf and "max_size = 30.0G"
> in ccache.conf, but cleanups are triggered when space usage reaches 24 GB,
> which is the default of 0.8. Why is this
Hi Venkat,
> cache hit(preprocessed) puts the .d file from the workspace as-is into the
> cache, thus, if such a compilation resulted in absolute paths in the .d
> file(in workspace), then, the cache will also contain .d files with
> absolute paths, resulting in troubles later on(from another
Hi Andreas,
> [...] I understand that it makes
> sense to make the current working directory canonic, but I do not
> see why this done for the path given to `make_relative_path`. Is
> it really necessary?
Some background can be found in this mail thread:
Hi Karanam,
> From just ccache's point of view, is there a way to force relative paths into
the
> .d files at all?
Yes, ccache version 3.3 and newer knows how to do this. See the release
notes for ccache 3.3: http://ccache.samba.org/releasenotes.html#_ccache_3_3
-- Joel
85 matches
Mail list logo