<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 6, 2013 at 6:20 AM, John Marino <span dir="ltr"><<a href="mailto:dragonflybsd@marino.st" target="_blank">dragonflybsd@marino.st</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 5/6/2013 14:52, Petr Janda wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Now, the _very_ interesting (and unexpected) part is the less than 2% pkgsrc<br>
packages usage.<br>
Maybe it's just that pkgng is so much better, maybe it's that pkgsrc users<br>
prefer to build software from source. Difficult to know.<br>
<br>
In any case, I don't see a reason to continue building pkgsrc packages with<br>
these numbers.<br>
</blockquote>
<br>
I wonder if this means clang should be included in base instead of GCC<br>
4.4. Since Ports are a FreeBSD thing, and they have switched to clang,<br>
more and more ports are going to build with it.<br>
</blockquote>
<br></div>
I'm not making the connection.<br>
For starters, just because FreeBSD has clang as a system compiler doesn't mean they use it to build packages.</blockquote><div><br></div><div>Clang is the default compiler for FreeBSD 10, and pkgng is the default package management tool as well. Thus, all packages for FreeBSD 10 are built using Clang, in pkgng format.<br>
<br></div><div>Clang is available as a compiler in FreeBSD 9, and pkgng is available as well. Both can be enabled via simple entries in /etc/make.conf and /etc/src.conf. Anyone is free to enable them and test them.<br><br>
There was a big push near the end of 2012 to get as many ports are possible to compile with Clang, and to add entries to port Makefiles to specify GCC if-and-only-if it wouldn't compile with Clang.<br><br>IOW, FreeBSD ports are almost all buildable using Clang, and the ports tree will default to Clang moving forward.<br>
</div></div><br>-- <br>Freddie Cash<br><a href="mailto:fjwcash@gmail.com">fjwcash@gmail.com</a>
</div></div>