Date: Mon, 17 Jun 2013 14:02:15 +0000 From: "Eggert, Lars" <lars@netapp.com> To: Bryan Drewery <bdrewery@freebsd.org> Cc: Dimitry Andric <dim@freebsd.org>, "current@freebsd.org" <current@freebsd.org> Subject: Re: ccache issues during buildworld on recent -CURRENT Message-ID: <46724BE4-A682-44E8-B980-C0143BD6AFC1@netapp.com> In-Reply-To: <51BF0669.60607@FreeBSD.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, 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 = it. Pity! We do buildworld often enough that that's an inconvenience. > 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. doesn't seem to help, unfortunately. > There are a few fixes in the ccache development repository that I have > been meaning to bring to our devel/ccache port. I'd be happy to test once there is something to test! Lars=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46724BE4-A682-44E8-B980-C0143BD6AFC1>