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 1O7c4F-00023p-0H for garchives@archives.gentoo.org; Thu, 29 Apr 2010 22:18:47 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 982F7E07A8; Thu, 29 Apr 2010 22:18:40 +0000 (UTC) Received: from smtp3-g21.free.fr (smtp3-g21.free.fr [212.27.42.3]) by pigeon.gentoo.org (Postfix) with ESMTP id CA8C3E0662 for ; Thu, 29 Apr 2010 22:18:11 +0000 (UTC) Received: from smtp3-g21.free.fr (localhost [127.0.0.1]) by smtp3-g21.free.fr (Postfix) with ESMTP id 01B2981805D for ; Fri, 30 Apr 2010 00:18:08 +0200 (CEST) Received: from [192.168.0.10] (bdv75-1-81-57-102-74.fbx.proxad.net [81.57.102.74]) by smtp3-g21.free.fr (Postfix) with ESMTP id B519E81807C for ; Fri, 30 Apr 2010 00:18:05 +0200 (CEST) Message-ID: <4BDA0541.8010401@gentoo.org> Date: Fri, 30 Apr 2010 00:16:33 +0200 From: =?UTF-8?B?UsOpbWkgQ2FyZG9uYQ==?= User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 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 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] ccache causing problems References: <4BD9300B.30103@gentoo.org> In-Reply-To: <4BD9300B.30103@gentoo.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 1e9acfc2-2941-481a-9a22-18660495beb7 X-Archives-Hash: 04212164934ea01de7f827f935062ce9 Le 29/04/2010 09:06, "Pawe=C5=82 Hajdan, Jr." a =C3=A9crit : > 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, R=C3=A9mi