public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Darragh Bailey <daragh.bailey@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ccache taking way too long time
Date: Fri, 30 Sep 2005 14:54:10 +0100	[thread overview]
Message-ID: <397042c80509300654508f27da@mail.gmail.com> (raw)
In-Reply-To: <a3c2e88b050929144413d3c69f@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 989 bytes --]

On 9/29/05, Fernando Meira <fmeira@gmail.com> wrote:
>
>
> # du -sh .ccache/
> 965M .ccache/
>
> # ccache -s
> cache hit 4569
> cache miss 32736
> called for link 3200
> multiple source files 7
> compile failed 618
> preprocessor error 209
> not a C/C++ file 1420
> autoconf compile/link 3617
> unsupported compiler option 1214
> no input file 2570
> files in cache 65472
> cache size 960.6 Mbytes
> max cache size 2.0 Gbytes
>
> Can it be just because it's inside root's dir?
>
> Cheers,
> Fernando
>

Depends on what features your using, but yes is probably the correct answer.


Not 100% certain about all the features that can have this affect but
userpriv would definitely prevent use of that ccache location when
compiling.

If it is enabled you can disable it and allow root to build, but personally
I think a better bet is to use a different location for the ccache.

--
Darragh Bailey
"Nothing is foolproof to a sufficiently talented fool"

[-- Attachment #2: Type: text/html, Size: 2963 bytes --]

  reply	other threads:[~2005-09-30 13:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-25 16:20 [gentoo-user] ccache taking way too long time Fernando Meira
2005-09-28 19:55 ` Tamas Sarga
2005-09-29 21:44   ` Fernando Meira
2005-09-30 13:54     ` Darragh Bailey [this message]
2005-09-30 16:38     ` Jason Stubbs
2005-09-30 20:48       ` Fernando Meira

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=397042c80509300654508f27da@mail.gmail.com \
    --to=daragh.bailey@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox