From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1O7cl4-0006Ng-9i for garchives@archives.gentoo.org; Thu, 29 Apr 2010 23:03:02 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2E93EE07AA; Thu, 29 Apr 2010 23:03:00 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 55D6FE0741 for ; Thu, 29 Apr 2010 23:02:54 +0000 (UTC) Received: from [10.42.0.7] (APuteaux-554-1-98-110.w92-154.abo.wanadoo.fr [92.154.9.110]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 7A9191B4051 for ; Thu, 29 Apr 2010 23:02:53 +0000 (UTC) Subject: Re: [gentoo-dev] ccache causing problems From: Gilles Dartiguelongue To: gentoo-dev@lists.gentoo.org In-Reply-To: <4BDA0541.8010401@gentoo.org> References: <4BD9300B.30103@gentoo.org> <4BDA0541.8010401@gentoo.org> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-R3fdMThbCGTxMBSHK4AT" Organization: Gentoo Date: Fri, 30 Apr 2010 01:02:48 +0200 Message-ID: <1272582168.17347.4.camel@keitaro.perronet.esiee.net> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.28.3.1 X-Archives-Salt: e6a29ebd-be9c-4119-b4e7-96e830567d03 X-Archives-Hash: 7de073ce6bf7154a3c3eb0d003ab0286 --=-R3fdMThbCGTxMBSHK4AT Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Le vendredi 30 avril 2010 =C3=A0 00:16 +0200, R=C3=A9mi Cardona a =C3=A9cri= t : > Le 29/04/2010 09:06, "Pawe=C5=82 Hajdan, Jr." a =C3=A9crit : > > What actions would you suggest? >=20 > Don't use ccache. We (speaking as a former gnome herd member) have had > countless unexplained bugs due to ccache. >=20 > 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. >=20 > 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. >=20 > 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. --=20 Gilles Dartiguelongue Gentoo --=-R3fdMThbCGTxMBSHK4AT Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?= -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) iEYEABECAAYFAkvaEBgACgkQ1fmVwcYIWAYnlwCgwSN49jkgMpJeR5Tsz0F2kpRF t4EAoNhy6NhhiWsI/wd9+hVixFWb7vjK =wsov -----END PGP SIGNATURE----- --=-R3fdMThbCGTxMBSHK4AT--