public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Gilles Dartiguelongue <eva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ccache causing problems
Date: Fri, 30 Apr 2010 01:02:48 +0200	[thread overview]
Message-ID: <1272582168.17347.4.camel@keitaro.perronet.esiee.net> (raw)
In-Reply-To: <4BDA0541.8010401@gentoo.org>

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

Le vendredi 30 avril 2010 à 00:16 +0200, Rémi Cardona a écrit :
> Le 29/04/2010 09:06, "Paweł Hajdan, Jr." a écrit :
> > What actions would you suggest?
> 
> Don't use ccache. We (speaking as a former gnome herd member) have had
> countless unexplained bugs due to ccache.
> 
> Now, the gnome procedure for build failures is to ask users to first
> disable distcc and ccache before trying to reproduce the bug, and that
> solves nearly all the weird issues that no-one else can reproduce.
> 
> Bottom line, unless you're building the same code over and over again,
> don't use ccache. And even if you are, don't use it, its cache is just
> too easily broken.
> 
> Cheers,

Not that countless. Personal experience reports one bug in 8 years of
use... Just as was previously mentioned in this thread:
 * check your hardware
 * know your FEATURES and howto test failures when some are enabled

it's just like any package failing with some gcc/linked/whatever flag,
you just don't stop using that flag where it works just because of one
package, nor do you stop using gcc.

-- 
Gilles Dartiguelongue <eva@gentoo.org>
Gentoo

[-- Attachment #2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2010-04-29 23:03 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 [this message]
2010-04-30 16:34     ` Robin H. Johnson
2010-05-03  8:49       ` [gentoo-dev] " Peter Hjalmarsson

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=1272582168.17347.4.camel@keitaro.perronet.esiee.net \
    --to=eva@gentoo.org \
    --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