Date: Sun, 17 Aug 2008 01:28:52 +0100 From: RW <fbsd06@mlists.homeunix.com> To: freebsd-questions@freebsd.org Subject: Re: Working ccache configuration for buildworld on amd64? 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 15 Aug 2008 11:22:01 -0400 "Maxim Khitrov" <mkhitrov@gmail.com> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080817012852.728a79ae>