I compile kernel packages for older PCs on my workstation. The builds are
highly similar differing only in the a few option within the .config file I use
for them (mainly differ cpu families). Will ccache mess up anything or is it
perfect for my use?
Example:
Kernel package 1: generic x86
Ker
fficient with disk space.)
So maybe this is best kept as a fork. Anyway it seemed like a good time
to take a straw poll to see if anyone was interested in those. Anyone?
Cheers,
John
Joel Rosdahl wrote:
> Hi Tridge and others,
>
> The latest ccache version was released over five y
d
close()d on host A, and subsequently open()ed on host B, that the second
open() will reflect all modifications and attributes from the close().
Since Make does open() when checking timestamps, and the dummy file is
close()d when it's created, the binary will always relink after the
object is recompiled.
Good luck.
John
This is a more elegant fix for NFS issues. It applies to ccache-2.4.
Unlike my previous patch, it doesn't create lock files, thereby avoiding
any issues with stale lock files.
- John
diff -u /home/jcoiner/ccache-2.4/ccache.c ccache-2.4_nfs_fix/ccache.c
--- /home/jcoiner/ccache-2.4/cca
NFS, which is a stateless protocol, the server
immediately forgets that the original A ever existed. When process Y
comes back requesting the next chunk of the original A, it is gone.
This patch prevents overwriting an object that's already in the cache.
It seems to work, YMMV.
- John
% of trials; with the workaround, I have not seen a failure in
>15 trials. So it might actually work.
- John
--- ccache-2.4/ccache.c 2004-09-13 06:38:30.0 -0400
+++ ccache-2.4-fix/ccache.c 2007-03-24 10:40:46.0 -0500
@@ -157,6 +157,7 @@
char *tmp_stdout, *tmp_
Ignore that patch -- this workaround does not work.
John Coiner wrote:
>
> Hi all,
>
> Here's a patch, for ccache 2.4, which works around the NFS bug. From the
> ccache man page:
>
> "BUGS. When the cache is stored on an NFS filesystem, the filesyst
