Stephan Kulow
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 10.06.2015 15:46, Richard Biener wrote:
On Wed, 10 Jun 2015, Stephan Kulow wrote:
Hi, ... [3] The how ... - and IMO we need to keep a defined compatibility with SLE 12. I don't know yet how that should look like, but we need to define use cases that should work and test it (something along "install the rpm of FOOBAR for sle12 on openSUSE 42 and start FOO to test BAR")
To add one of the more interesting challenges here is that iff we succeed in adapting to a compiler other than the GCC 4.8 based one on SLE 12 we face the issue that with GCC 5 the libstdc++6 "default" ABI changed and thus you can't mix programs or libraries built with the old ABI with ones built with the new ABI (well, that's a simplified statement, of course).
Now, it might be that openSUSE 42 is not a "add-on" and thus we re-build all packages anyway, even those that are still the same as in SLE 12.
Updating the compiler for old SLE 12 packages might be a challenge on itself, of course. And I don't think we want to go there. I'm sure you see it differently, but the net value of a new compiler to a random openSUSE user is very small - not worth the trouble inherited with it.
Only clang >= 3.4 & gcc >= 4.9 provide true C++14 support so two leechcraft subpackages can't be build even for openSUSE:Factory just now. More and more package will became non-buildable in the future. Actual Qt5 would be fine too.
So - if the compiler used for building packages stays GCC 4.8 based for the lifetime of openSUSE 42 then any additional compiler we ship has to default to the old libstdc++6 ABI (which is at least possible for GCC 5).
That sounds like a plan actually :)
Greetings, Stephan
-- Best regards, Dmitriy DA(P).DarkneSS Perlow @ Linux x64 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org