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 1O7ONz-0003Xl-7D for garchives@archives.gentoo.org; Thu, 29 Apr 2010 07:42:15 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3D6A5E081D; Thu, 29 Apr 2010 07:42:10 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 78550E0784 for ; Thu, 29 Apr 2010 07:41:59 +0000 (UTC) Received: from mail.isohunt.com (b01.ext.isohunt.com [208.71.112.51]) by smtp.gentoo.org (Postfix) with ESMTP id EDE161B400B for ; Thu, 29 Apr 2010 07:41:58 +0000 (UTC) Received: (qmail 18583 invoked from network); 29 Apr 2010 07:41:53 -0000 Received: from tsi-static.orbis-terrarum.net (HELO grubbs.orbis-terrarum.net) (76.10.188.108) by mail.isohunt.com (qpsmtpd/0.33-dev on beta01) with (CAMELLIA256-SHA encrypted) ESMTPS; Thu, 29 Apr 2010 07:41:53 +0000 Received: (qmail 6091 invoked by uid 10000); 29 Apr 2010 07:41:51 -0000 Date: Thu, 29 Apr 2010 07:41:51 +0000 From: "Robin H. Johnson" To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] ccache causing problems Message-ID: References: <4BD9300B.30103@gentoo.org> 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 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <4BD9300B.30103@gentoo.org> User-Agent: Mutt/1.5.20 (2009-06-14) Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 04626343-cee1-4385-a0ae-906aa9a45e5f X-Archives-Hash: 5ec9b66f034af43b19f3dca1f7c1df9e On Thu, Apr 29, 2010 at 09:06:51AM +0200, "Pawe=C5=82 Hajdan, Jr." wrote: > What actions would you suggest? Have your user do a binary search of the ccache dir to find which cache file is causing the problem, by restoring from his backup then renaming half the directories each time. Then tie that to what the input file should have generated it. Most of the problems I've seen have been due to a disk or OS error causing the cache output file to be corrupt or empty, instead of the expected object code. ccache itself hasn't been the problem, but unreliable hardware has. Provably by removing the corrupt cache files, then running with ccache a few more times, and having everything work perfectly. --=20 Robin Hugh Johnson Gentoo Linux: Developer, Trustee & Infrastructure Lead E-Mail : robbat2@gentoo.org GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85