In summary: to make ccache work safely on an NFS filesystem, the
filesystem must be exported with no_subtree_check. Otherwise data can
be lost when it renames recently-written files. :-(
--
Begin forwarded message:
Date: 27 Aug 2003 21:37:38 -0400
From: Trond Myklebust
On 10 Aug 2003, Koblinger Egmont egm...@uhulinux.hu wrote:
./out/axis.o: axis.cc include/axes.hh include/string.hh \
include/arithmetic-operator.hh include/flower-proto.hh include/real.hh \
include/string-handle.hh include/string-handle.icc \
include/string-data.hh
If I run ccache 2.2 on a .i file, it thinks it's not a C/C++ file and
it doesn't cache it.
This could be naively fixed by updating check_extension(), but it
would be far better for ccache to know that it doesn't need to run cpp
on such files. distcc does so.
In particular this means that if
Enno Rehling wrote:
we're considering using ccache and sharing the cache between
developers here. I've followed the instructions in the manpage, but
ccache doesn't seem to realize that the object file is already in the
cache, and compiles a new one for every user.
- The output files have
Sorry, I don't understand what you're trying to say.
Sorry for my english but may i try again.
the ccache program works perfectly for me.
on a machine first compile something it add its work to the cache
and the second time a compile the same source it takes the objects from the
cache what
Or perhaps ccache should just cache stdout. distcc sends it across
the network alongside stderr.
I'm not sure why writing to stdout forces a cache miss.
It's because is also very hard to accurately cache both stderr and
stdout because of the timing of lines between them. To really
I was just about to start using ccache with distcc and didn't know the best way
to go about, only to discover a just-in-time release that makes it easy! Thanks!
Last week we started to use the Intel compiler in parallel with gcc. The Intel
compilers produce a number of cool but unnecessary
I released ccache 2.0 a couple of days ago, and have done two minor
releases since then to fix small bugs that were noticed in the 2.0
release.
Main changes are:
- minor Makefile install fixes
- fixed some compilation warnings
- added -C option for 'clear cache completely'
- added CCACHE_CC
ccache: version 2.2
OS: Windows XP Professional
cygwin: latest version
Hello,
first of all: we like ccache - its a great utlility - thanks a lot!
We're using ccache to share compiler output between several people.
All works fine - but if the ccache file server is not available - it would be
On 31 Oct 2003, Brian Poynor bri...@redback.com wrote:
Is CCACHE_PREFIX intentionally included in the hash?
Yes.
For my project it means that objects built locally never match objects
built remotely with CCACHE_PREFIX=distcc, even though they are
identical, and I'd like to avoid duplicate
Hello,
I've just started to use this cool tool, but came up with the following problem:
If I run ccache from my local machine I build a cache, where if I rebuild the
same [unchanged]
files, every file is hit in the cache. If I then set the following environment
variable:
CCACHE_PREFIX=distcc
On 23 Sep 2002, Tim Potter t...@samba.org wrote:
Hi Tridge. I've just had some distcc/ccache wierdness that caused my
ccache to be corrupted. One of the machines in our DISTCC_HOSTS list
filled up /tmp and a whole bunch of object files were created containing
text like:
On Fri, Nov 21, 2003 at 03:28:32PM -0800, Sean Gies wrote:
2. Added a check to the argument processing logic to handle this sort
of invocation:
/usr/share/bin/ccache /usr/bin/distcc /usr/bin/gcc-3.3 ...
In order to handle multiple compiler versions, Xcode uses full paths to
invoke
Looks like mailman ate my attachment. Here's the patch again: EOT
Index: ccache.c
===
RCS file: /cvsroot/ccache/ccache.c,v
retrieving revision 1.91
diff -u -r1.91 ccache.c
--- ccache.c28 Sep 2003 04:47:59 - 1.91
+++
Here's a patch I created so that I can use ccache with Apple's Xcode
IDE.
1. Added more extensions to better support Objective-C and
Objective-C++.
2. Added a check to the argument processing logic to handle this sort
of invocation:
/usr/share/bin/ccache /usr/bin/distcc
ccache: version 2.2
distcc: version 2.11
OS: Windows XP Professional
cygwin: latest version
Hello,
I' using the calling distcc with the full compiler name cause of using different
cross compiler versions
for example compiling distcc distribution (using native gcc it's just the same
behaviour):
On 1 Oct 2003, andrew andrew.sla...@discus.anu.edu.au wrote:
Hi,
Should ccache always ignore compiles with (g++) -frepo, since object
files might have to be rebuilt at link time, due to c++ template object
code placement? I bypassed caching for -frepo'd source files so my
template stuff
Hi,
I've just released ccache 2.3. Grab it from http://ccache.samba.org/
The checksum generated by 2.3 is not compatible with previous ccache
versions. (I'm using ccache since 1.9 and it was always compatible.)
When I compile something, upgrade ccache from 2.2 to 2.3, and recompile it
again,
I've just released ccache 2.3. Grab it from http://ccache.samba.org/
Major changes:
* Added CCACHE_UMASK option
* Added support for compilation of .i files
* Fixed bug with DEPENDENCIES_OUTPUT flag
* Added support for more -Mx options
* Added separate stderr channel for distcc
* Improved
On Wed, 24 Sep 2003 ee...@gmx.net wrote:
+ close(creat(path_stderr, 0644));
Should be 0666, the rest is the job of umask.
--
Egmont
+ } else {
+ copy_file(input_file, path_stdout);
+ x_asprintf(command, touch %s, path_stderr);
+ system(command);
+ free(command);
+ }
Huh?
i know, it's been a while since i last did c. i'm sure there are
faster ways to provide
On 23 Sep 2003, ee...@gmx.net wrote:
on Mon, 21 Jul 2003 23:52:45 -0700, Martin Pool wrote:
If I run ccache 2.2 on a .i file, it thinks it's not a C/C++ file and
it doesn't cache it.
This could be naively fixed by updating check_extension(), but it
would be far better for
22 matches
Mail list logo
