From owner-freebsd-questions@FreeBSD.ORG Sun Aug 17 00:45:51 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CCEA01065687 for ; Sun, 17 Aug 2008 00:45:51 +0000 (UTC) (envelope-from fbsd06+Y4=c3ff49eb@mlists.homeunix.com) Received: from fallback-in1.mxes.net (fallback-out1.mxes.net [216.86.168.190]) by mx1.freebsd.org (Postfix) with ESMTP id 994E08FC08 for ; Sun, 17 Aug 2008 00:45:51 +0000 (UTC) (envelope-from fbsd06+Y4=c3ff49eb@mlists.homeunix.com) Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178]) by fallback-in1.mxes.net (Postfix) with ESMTP id 84F4A163F6B for ; Sat, 16 Aug 2008 20:28:57 -0400 (EDT) Received: from gumby.homeunix.com. (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 0A7F123E405 for ; Sat, 16 Aug 2008 20:28:55 -0400 (EDT) Date: Sun, 17 Aug 2008 01:28:52 +0100 From: RW To: freebsd-questions@freebsd.org Message-ID: <20080817012852.728a79ae@gumby.homeunix.com.> In-Reply-To: <26ddd1750808150822r334f800bs73a1117bf310be11@mail.gmail.com> References: <26ddd1750808141304x46ed9e6dhe5bf04363a41626b@mail.gmail.com> <20080815154838.16f391a9@gumby.homeunix.com.> <26ddd1750808150822r334f800bs73a1117bf310be11@mail.gmail.com> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.11; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Working ccache configuration for buildworld on amd64? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Aug 2008 00:45:51 -0000 On Fri, 15 Aug 2008 11:22:01 -0400 "Maxim Khitrov" wrote: > I think what's happening is that there is a collision in hash values > generated by ccache. That's the only thing I can think of, because > crt1.c is compiled twice; once from /usr/src/lib/csu/amd64/crt1.c, and > a second time from /usr/src/lib/csu/i386-elf/crt1.c. If LIB32 is > disabled in src.conf, only the first compilation takes place. If the > generated hash values are the same, by some chance, then the actual > problem is that the file is not compiled a second time when, in fact, > it should be. This is only a guess, however. That collision isn't going to happen for several reasons, but it's missing the point I made earlier, that the build is failing on a cache miss. If the kind of situation you're describing is happening, then it's happening earlier, and the observed error is just a side-effect.