Date: Sat, 24 Aug 2013 10:52:20 +0100 From: David Chisnall <theraven@FreeBSD.org> To: Julian Elischer <julian@FreeBSD.org> Cc: freebsd-current@FreeBSD.org Subject: Re: GCC withdraw Message-ID: <BBAB67AC-3073-4711-A000-5D7B34462544@FreeBSD.org> In-Reply-To: <52180DD0.3080308@freebsd.org> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5217413A.9080105@passap.ru> <20130823111647.GT2951@home.opsec.eu> <52174D51.2050601@digsys.bg> <21414.1377258940@critter.freebsd.dk> <5217A7D8.1030806@freebsd.org> <1377285836.31114.13416825.5F534A08@webmail.messagingengine.com> <52180DD0.3080308@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 24 Aug 2013, at 02:35, Julian Elischer <julian@freebsd.org> wrote: > I don't know.. whatever RootBSD run, but the fact that I needed gcc = for anything suggests that we should keep it around for a while. Please point to the FreeBSD PRs and clang bug reports that you have = filed about this. I have been running a FreeBSD VM on Xen with the = clang is cc option for over a year and not encountered this problem. David
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BBAB67AC-3073-4711-A000-5D7B34462544>