Another C++ ABI change?

[David Tardon]

Hi,

On Fri, Apr 10, 2015 at 07:26:58AM +0200, Markus Trippelsdorf wrote:
> On 2015.04.10 at 00:48 +0200, Michael Schwendt wrote:
> > On Thu, 09 Apr 2015 11:40:17 -0600, Orion Poplawski wrote:
> > 
> > > With gcc 5.0.0-0.22.fc23 I'm getting new build failures:
> > 
> > > /builddir/build/BUILD/gdl-0.9.5/src/magick_cl.cpp:175: undefined reference to
> > > `Magick::Image::magick[abi:cxx11]() const'
> > > 
> > > Did we just get another set of C++ ABI changes?
> > 
> > I would say "yes", since more C++ libs are affected.
> 
> Jason added automatic ABI tagging for functions with (e.g.) std::string
> return type. See: http://thread.gmane.org/gmane.comp.gcc.patches/337867/
> This not only breaks compatibility with clang, but also with all
> libraries that were compiled with gcc-5 before this commit. So you have
> to rebuild them all again.

My interpretation: the gcc team has once again pushed an ABI-breaking
change without any announcement and without any intention to handle the
necessary rebuilds. Sorry, dear gcc team, but that is not the way we
usually do things here...

Why didn't you wait for mass rebuild and only built the incompatible gcc
into the mass rebuild's tag? Then there would have been no breakage...

D.