On Tue, 15 Jun 2010 22:15:06 +0200 Michał Masłowski <m...@mtjm.eu> wrote:
> >Intersting idea. I have little experience with ccache. It's only > >useful > > from the second time on a package is compiled, right? Builder > > normally compiles a package only once. I'm curious to know what the > > ccache penalty is. If it makes Builder run a lot longer I'd rather > > not include it by default. > > > > I guess ccache only works when the binaries are not removed between > > compiles. Builder removes $WORKINGDIR every time before building a > > package. Can you explain how ccache can do its thing then? > ccache has its own cache of results of compilation of preprocessed C > source (depending on compiler version and arguments). It is designed > just for situations when $WORKINGDIR is removed before compilations. your patch only affects the chroot, so is the cache being stored in the chroot? if it is then its inside workingdir and gets removed. kk -- Karl Goetz, (Kamping_Kaiser / VK5FOSS) Debian contributor / gNewSense Maintainer http://www.kgoetz.id.au No, I won't join your social networking group
signature.asc
Description: PGP signature
_______________________________________________ gNewSense-dev mailing list gNewSense-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/gnewsense-dev
