On Mon, 10 Aug 2015, Jakub Wilk wrote:
Perhaps this issue is due to g++ defaulting to a newer version of the C++
standard and thus it requires a new C++ ABI?
I don't think so. I'd rather blame:
* Test build with QuantumDepth 16 (closes: #557879).
But wait, isn't change of QuantumDepth an ABI breakage?
SONAME of the non-C++ library didn't change; it's still
/usr/lib/libGraphicsMagick.so.3.
If --enable-quantum-library-names was used as an option to the
configure script, then the shared library name would become like
libGraphicsMagick-Q16.so so the whole run-time library name is
different. If the QuantumDepth 8 build did not use this option, then
it would be named as before and existing apps (compiled with
QuantumDepth 8) should work with it. This allows the libraries to
co-exist.
The package used for development needs to specify if it is for Q8
or Q16 since (barring other factors), it is only possible to develop
for one at a time.
Regardless, if GCC 5.X is now being used (is this the case?), I would
suspect that the C++ default ABI (and libraries) have changed (to C++
11) and this results in different name mangling. Note that the linker
did find the library but not the method.
Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
