Date: Mon, 17 Jun 2013 09:05:25 -0500 From: Bryan Drewery <bdrewery@FreeBSD.org> To: "Eggert, Lars" <lars@netapp.com> Cc: Dimitry Andric <dim@freebsd.org>, "current@freebsd.org" <current@freebsd.org> Subject: Re: ccache issues during buildworld on recent -CURRENT Message-ID: <9DEFB40E-8DEA-4AF3-89D8-BF272D1CB402@FreeBSD.org> In-Reply-To: <46724BE4-A682-44E8-B980-C0143BD6AFC1@netapp.com> References: <7DBA8962-9108-489E-81EA-ECE8D72698D1@netapp.com> <519CADE5.5020908@FreeBSD.org> <743F375A-F0C1-466E-8E34-E1319FFD9045@netapp.com> <628177EC-5207-49F4-9546-47784F56CB43@netapp.com> <51BF0669.60607@FreeBSD.org> <46724BE4-A682-44E8-B980-C0143BD6AFC1@netapp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 17, 2013, at 9:02, "Eggert, Lars" <lars@netapp.com> wrote: > Hi, >=20 > On Jun 17, 2013, at 14:51, Bryan Drewery <bdrewery@freebsd.org> wrote: >> ccache is known to be broken with clang [1]. I would recommend not using i= t. >=20 > Pity! We do buildworld often enough that that's an inconvenience. I have been using -DNO_CLEAN for buildworld for now. Results have been prett= y good. >=20 >> Sometimes CCACHE_CPP2=3D1 in make.conf can help. CCACHE_CPP2=3D1 is >> hardcoded in version 3.1.9_2 of devel/ccache on CURRENT. There are other >> classes of problems that are not fixed in upstream ccache yet. >=20 > doesn't seem to help, unfortunately. >=20 >> There are a few fixes in the ccache development repository that I have >> been meaning to bring to our devel/ccache port. >=20 > I'd be happy to test once there is something to test! >=20 > Lars
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9DEFB40E-8DEA-4AF3-89D8-BF272D1CB402>