On Wednesday, 30 January 2013, Walter Bender wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, Jan 30, 2013 at 5:59 AM, Daniel Narvaez <<a href="javascript:;" onclick="_e(event, 'cvml', 'dwnarvaez@gmail.com')">dwnarvaez@gmail.com</a>> wrote: > I think it's probably ccache corruption. > > ccache -C > rm -rf build/metacity > make build > That seems to have fixed things. I hadn't realized that gcc had such aggressive caching. I'd done a fresh clone after my first failure and had gotten the same error. Well, it is working now. Thanks very much. </blockquote><div> </div><div>It doesn't actually :) ccache is something sugar-build adds on top gcc. It's normally a very reliable tool and it speeds up a lot clean builds. Though I'm debating a bit about turning it off by default now. I and buildbot are doing lots of clean builds but I suppose most developers are not. I'm not sure how often this kind of problems happen... Maybe let's wait someone reporting it again before turning it off :)</div> -- Daniel Narvaez