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.
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).
Richard.
--
Richard Biener