From: Peter Hjalmarsson <xake@rymdraket.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: ccache causing problems
Date: Mon, 03 May 2010 10:49:28 +0200 [thread overview]
Message-ID: <1272876568.19261.4.camel@lillen> (raw)
In-Reply-To: <robbat2-20100430T162632-628708771Z@orbis-terrarum.net>
fre 2010-04-30 klockan 16:34 +0000 skrev Robin H. Johnson:
> Note however, that while I have a high level of trust in ccache, I do
> think there are more latent bugs in distcc.
>
Heh, yeah. I have had problems with ccache having broken cache (i.e.
stuff breaks, removing the cache and it unbreaks) on different
computers, but since I stopped use distcc together with it I have had no
such problems anymore.
Still since those experiences I always start with trying without ccache
when I hit strange bugs.
prev parent reply other threads:[~2010-05-03 8:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 7:06 [gentoo-dev] ccache causing problems "Paweł Hajdan, Jr."
2010-04-29 7:41 ` Robin H. Johnson
2010-04-29 7:48 ` "Paweł Hajdan, Jr."
2010-04-29 7:51 ` Ciaran McCreesh
2010-04-29 8:32 ` Robin H. Johnson
2010-04-29 22:16 ` Rémi Cardona
2010-04-29 22:34 ` Jorge Manuel B. S. Vicetto
2010-04-29 23:02 ` Gilles Dartiguelongue
2010-04-30 16:34 ` Robin H. Johnson
2010-05-03 8:49 ` Peter Hjalmarsson [this message]
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=1272876568.19261.4.camel@lillen \
--to=xake@rymdraket.net \
--cc=gentoo-dev@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