Date: Thu, 13 Sep 2012 01:22:46 +0200 (CEST) From: Gerald Pfeifer <gerald@pfeifer.com> To: toolchain@freebsd.org Cc: current@freebsd.org Subject: Re: Clang as default compiler November 4th Message-ID: <alpine.LNX.2.00.1209130121160.1687@tuna.site> In-Reply-To: <848C813E-E6EC-4FAF-9374-B5583A077404@cederstrand.dk> References: <20120910211207.GC64920@lor.one-eyed-alien.net> <20120911104518.GF37286@deviant.kiev.zoral.com.ua> <20120911120649.GA52235@freebsd.org> <20120911122122.GJ37286@deviant.kiev.zoral.com.ua> <20120911123833.GA54483@freebsd.org> <848C813E-E6EC-4FAF-9374-B5583A077404@cederstrand.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 11 Sep 2012, Erik Cederstrand wrote: > So can we do a sweep on the ports tree and mark the 2232 ports with > USE_GCC=4.2 until they can actually build with clang? This could allow > the clang switch to proceed. Hopefully, waiting for GCC to compile just > to install some tiny port will be enough of a nuisance for people to > eventually fix the remaining ports. To make it less painful, I just adjusted lang/gcc42 to not boostrap any more, rather just build. This allows for a full build in ten or less minutes on an old quad core I used for testing. Gerald
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.LNX.2.00.1209130121160.1687>