svn commit: r270099 - in stable: 10/contrib/gcc/config/i386 9/contrib/gcc/config/i386

Pedro Giffuni pfg at
Tue Aug 19 04:06:07 UTC 2014

Il giorno 18/ago/2014, alle ore 20:31, Alexey Dokuchaev <danfe at> ha scritto:

> On Mon, Aug 18, 2014 at 02:27:21PM -0500, Pedro Giffuni wrote:
>> I personally stopped merging stuff to the stable/8 branch and more recently
>> to the stable/9 branch as I don't run those anymore. In the case of the
>> stable/8 branch I find the ancient version of binutils a real threat/
>> limitation.
> Contemporary version of binutils can be installed from the port, right?  I
> don't have a problem with it since binutils are relatively fast to build
> and releases do not happen that often to become annoying.

We are talking about updates to the base that may be affected by the binutils version.
I have no idea if the base system in stable/8 will work with the version in ports but
still that doesn’t solve the issue one might have merging code that expects binutils
2.17.1+ and that will therefore break the tinderbox.

>> I would really suggest people move on to at least stable/9 which has all
>> the clang cleanups and should be functionally much better.
> Clang/LLVM is a nuisance to build, which is one of the reason to avoid 9+
> on my rusty laptop.  I run -CURRENT more or less happily on modern hardware.

I meant 9.x has cleanups that make the base system build cleanly with both clang and gcc.
8.x has been lagging many suchcleanups.
You can disable building clang in /etc/src.conf, and I actually do that when testing crossbuilds.


More information about the svn-src-all mailing list