Hundreds Of Ubuntu Packages Are Failing To Build With GCC 6

[phoronix]

Phoronix: Hundreds Of Ubuntu Packages Are Failing To Build With GCC 6

Debian/Ubuntu developer Matthias Klose has run a test rebuild of Ubuntu Linux re-compiled under the in-development GCC 6 compiler...

http://www.phoronix.com/scan.php?page=news_item&px=GCC6-Ubuntu-Rebuild

[zanny]

It took 10 years for GCC 5.0 to come out after 4.0, but we are getting 6.0 a year later?

Seriously GCC, slow the fuck down. This seems like a blatant mistake, because all these changes that are causing such massive breakages now should have held back GCC 5 so we would have had one major release.

That being said, having the next major LTS stuck on 5.x for five years is going to be a PITA for developers using new GCC features in new projects in... 2020.

[Michael]

It took 10 years for GCC 5.0 to come out after 4.0, but we are getting 6.0 a year later?

Seriously GCC, slow the fuck down. This seems like a blatant mistake, because all these changes that are causing such massive breakages now should have held back GCC 5 so we would have had one major release.

That being said, having the next major LTS stuck on 5.x for five years is going to be a PITA for developers using new GCC features in new projects in... 2020.

As mentioned in many Phoronix articles now, the GCC versioning scheme changed with new GCC x.y releases coming out every year with .y being point releases and X being the major annual update.

[Serafean]

Seriously GCC, slow the fuck down. This seems like a blatant mistake, because all these changes that are causing such massive breakages now should have held back GCC 5 so we would have had one major release.

I wonder what percentage of these "regressions" is actually GCC catching more errors/being more strict...

[Candy]

Hundreds Of Ubuntu Packages Are Failing To Build With GCC 6

Uhm ? GCC 6 needs to be fixed then or stop doing experiments when releasing a new distro.

[linuxcbon]

Uhm ? GCC 6 needs to be fixed then or stop doing experiments when releasing a new distro.

maybe it's not gcc's fault but the softwares' fault ?

[pal666]

It took 10 years for GCC 5.0 to come out after 4.0, but we are getting 6.0 a year later?

Seriously GCC, slow the fuck down. This seems like a blatant mistake, because all these changes that are causing such massive breakages now should have held back GCC 5 so we would have had one major release.

seriously, moron, educate yourself before posting uninformed bullshit
6 after 5 is like 4.1 after 4.0, they just started to use one digit less
and gcc does one release every spring for long time already

[jgreenhalgh]

Uhm ? GCC 6 needs to be fixed then or stop doing experiments when releasing a new distro.

To be clear, a full distro rebuild like that doko just did is a usual part of testing GCC in preparation for a release. GCC has historically been released some time around April and the time between now and April will be used to fix the bugs that have just been reported and to run more full distro rebuilds. The number of failing packages does not necessarily indicate the work required to fix the compiler - consider that a single bug might break a number of packages.

Having compiler bugs reported during the compiler-bug-hunting-and-fixing phase of GCC development is perfectly healthy! That these reports come from major distributions shows what a huge "testsuite" GCC makes use of, across a number of architectures, to ensure that the compiler is as good as it can be when it is released!

This article is an interesting insight in to what we use to test GCC, but I wouldn't read too much in to the numbers at this stage.

I wonder what percentage of these "regressions" is actually GCC catching more errors/being more strict...

Some may have come from the misleading indentation warnings breaking Werror builds from the packages, others will just be compiler bugs that need fixing.

[andre30correia]

It took 10 years for GCC 5.0 to come out after 4.0, but we are getting 6.0 a year later?

Seriously GCC, slow the fuck down. This seems like a blatant mistake, because all these changes that are causing such massive breakages now should have held back GCC 5 so we would have had one major release.

That being said, having the next major LTS stuck on 5.x for five years is going to be a PITA for developers using new GCC features in new projects in... 2020.

with ubuntu simply use the toolchain ppa

[Alliancemd]

Too all those uninformed that complain about GCC 6 right now...

-Wall + -Werror + GCC 6 has more checks = Good, very good! But that makes packages with problems in their code to fail... Which is actually good. Forces them to fix problems.