Linked by Thom Holwerda on Thu 12th Jan 2012 22:54 UTC
FreeBSD Some people already submitted this news last week, but it wasn't until today that it became official: the FreeBSD team has announced the release of FreeBSD version 9.0. As you may expect from the major version number change, this is releas eis packed with new stuff.
Thread beginning with comment 503068
To view parent comment, click here.
To read all comments associated with this story, please click here.
0brad0
Member since:
2007-05-05

You need to watch the LLVM video regarding FreeBSD - it has nothing to do with 'loving' or 'hating' anything but the reality that there are some companies that use FreeBSD which have a no GPL3 or GPL policy and thus it is one area that needs to be addressed.


The project needs an up to date and maintainable compiler/toolchain that meets the projects requirements and with GCC past 4.2.1/binutils past 2.17 that is no longer possible. It's a much bigger issue than just some companies having an issue with GPL'd code.

Reply Parent Score: -1

Valhalla Member since:
2006-01-24


The project needs an up to date and maintainable compiler/toolchain that meets the projects requirements and with GCC past 4.2.1/binutils past 2.17 that is no longer possible. It's a much bigger issue than just some companies having an issue with GPL'd code.

Stop with the bs, the ONLY reason the BSD's didn't upgrade past 4.2.1 is because of the GPLv3 licence and as others have already stated this was because of companies supporting BSD having a 'no GPLv3 policy' (most likely due to the TIVO-ization clause).

Also this relates to what the BSD's ship with, all later GCC versions have been readily available through ports so those who have no problem with GPLv3 and wants to enjoy benefits of later versions like better optimization/faster compilation can get them.

Reply Parent Score: 4

0brad0 Member since:
2007-05-05


Stop with the bs, the ONLY reason the BSD's didn't upgrade past 4.2.1 is because of the GPLv3 licence and as others have already stated this was because of companies supporting BSD having a 'no GPLv3 policy' (most likely due to the TIVO-ization clause).

Also this relates to what the BSD's ship with, all later GCC versions have been readily available through ports so those who have no problem with GPLv3 and wants to enjoy benefits of later versions like better optimization/faster compilation can get them.


It's not bs. GPLv3 is not acceptable for the base OS. I can't help it if you cannot accept that the project has requirements and actually sticks to the requirements. It also goes beyond just the license when
it comes to using and maintaining the compiler.

The base OS compiler is what counts the most. It's a concept that seems to be lost on Linux people.

Reply Parent Score: 3