Jul 20, 2012

GCC 4.7 C++ ABI changes and openSUSE 12.2

GCC 4.7 introduced two changes that resulted in different ABIs (Application Binary Interface) for files that were compiled with C++98 versus files that were compiled using C++11 options. This could result in crashing applications, like bug bnc#767666 where "a C++98 library picked up a std::list operator= from a c++11 library resulting in a crash."

openSUSE 12.2 has been hit some of these incompatibilities in the update stack and the GCC developers now updated the compiler collection for openSUSE 12.2 to the current GCC 4.7 branch head which includes fixes for the two known issues. Those changes will also be in the upcoming GCC 4.7.2 release.

Every binary that uses std::list or std::pair in C++11 mode was effected and Coolo decided to rebuild the complete openSUSE 12.2 distribution to catch really everything - besides the known problems with the update stack and LibreOffice. This rebuild has been done after RC1 and therefore if you update from openSUSE 12.2 RC1 to RC2, you will see updates for many packages since they were recompiled.

This is also a warning - if you're using GCC 4.7.0 or 4.7.1 without this fix and compile programs using C++11 mode, update your compiler and recompile.

Some background

By default GCC compiles C++ programs using the options "-std=gnu++98" which is the GNU dialect of C++98. To build for the new C++11 standard, you have to specify "-std=c++11".

Details from the GCC changes pagel:
"GCC versions 4.7.0 and 4.7.1 had changes to the C++ standard library which affected the ABI in C++11 mode: a data member was added to std::list changing its size and altering the definitions of some member functions, and std::pair's move constructor was non-trivial which altered the calling convention for functions with std::pair arguments or return types. The ABI incompatibilities have been fixed for GCC version 4.7.2 but as a result C++11 code compiled with GCC 4.7.0 or 4.7.1 may be incompatible with C++11 code compiled with different GCC versions and with C++98/C++03 code compiled with any version."

Thanks

The fixing included many GCC jdevelopers, I'd like to give a special thank you to Richard G√ľnther und Michael Matz for debugging the issues in openSUSE and helping to get them fixed both upstream for GCC 4.7.2 and in openSUSE's GCC.

Jul 13, 2012

openSUSE 12.2 vs Factory Development

On the factory mailing list there has been some discussion about testing for openSUSE 12.2, so let me try to summarize the situation again: Coolo has split off the 12.2 distribution and its building on its own in the openSUSE Build Service as project openSUSE:12.2. Factory is its own project as usual.

Check-in

There are two ways to get packages into openSUSE 12.2 right now: The one way is to create a maintenance request against openSUSE 12.2 - the same way it's done for released distributions. The other way is a submission to factory, the release team reviews all submissions for Factory and decides which ones to take for 12.2 as well. So, if you really want your change in 12.2, you better state it as part of the submit message and write an entry for changes that makes the release team want the change.

Publishing

The openSUSE maintenance team likes to get everything - but the packages that went in via maintenancerequests as well as the packages that went in via Factory - out as updates. So, if you have the 12.2 and the 12.2-non-oss repositorires (from http://download.opensuse.org/update/ as repositories, you'll stay up to date.
Once RC2 is published, a full tree gets published together with new ISOs.
Note, that we now split the update repository to have a separate update repository for packages that are not Open Source.
Update 2012-07-14: During an installation of openSUSE 12.2 RC1, you get already the path of the 12.2 repositories. If you don't have them, enter directly as repository  http://download.opensuse.org/distribution/12.2/repo/oss/ and http://download.opensuse.org/distribution/12.2/repo/non-oss/. The links are redirects right now and point to RC1 - and will be updated with future releases.

Factory development

So, this also means that Factory is open for intrusive changes. I ask everybody to concentrate on making a great openSUSE 12.2 but the work for 12.3 can go in now.