Date: Wed, 21 Nov 2012 22:31:24 -0500 From: Steve Wills <swills@FreeBSD.org> To: AN <andy@neu.net> Cc: freebsd-current@FreeBSD.org Subject: Re: -Current built with clang as default + ports Message-ID: <50AD9C8C.9000703@FreeBSD.org> In-Reply-To: <alpine.BSF.2.00.1211131832240.22096@mail.neu.net> References: <mailman.3.1351857600.2182.freebsd-current@freebsd.org> <alpine.BSF.2.00.1211131832240.22096@mail.neu.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/13/12 18:51, AN wrote: > Can anyone comment on current built with clang as default compiler and > ports? Are there any major problems, programs that don't run? > Specifically, I am interested in how Gnome and Xorg (Gnome and Xorg > built with default system gcc) work on world built with clang. I can't comment on Gnome, but I run current on my desktop and use KDE4. I had to patch a few ports to build. Those patches have been sent in as PRs. Overall, the switch to ports built with clang was amazingly uneventful. So far, I haven't noticed anything that built but didn't work properly. > I believe the work around for ports that don't build with clang is to > put USE_GCC=4.7+ in the port makefile, is this correct? Any comments > would be appreciated, thanks in advance. A good bit of fixing for clang has already been done. I was able to fix pretty much everything I encountered that didn't build with clang, so didn't have to set USE_GCC anywhere, but it's there as a "last resort." Of course, those are just my experiences, YMMV. Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50AD9C8C.9000703>