gnewsense-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnewsense-dev] ccache support patch for the Builder


From: Dmitry Samoyloff
Subject: Re: [Gnewsense-dev] ccache support patch for the Builder
Date: Sat, 19 Jun 2010 17:47:55 +0400
User-agent: Wanderlust/2.14.1 (Bad Medicine-pre) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (Gojō) APEL/10.7 Emacs/23.1 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO)

At Sat, 19 Jun 2010 16:33:31 +0930,
Karl Goetz wrote:
> 
> [1  <multipart/signed (7bit)>]
> [1.1  <text/plain; UTF-8 (quoted-printable)>]
> On Tue, 15 Jun 2010 22:15:06 +0200
> Michał Masłowski <address@hidden> 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

No, the ccache cache is in /var/lib/ccache in chroot. The WORKINGDIR is
/srv/gnewsense/tmp in chroot.

I'm an FSF member -- Help us support software freedom!
<http://www.fsf.org/jf?referrer=7253>

> -- 
> Karl Goetz, (Kamping_Kaiser / VK5FOSS)
> Debian contributor / gNewSense Maintainer
> http://www.kgoetz.id.au
> No, I won't join your social networking group



reply via email to

[Prev in Thread] Current Thread [Next in Thread]