Bug#853598: opensaml2: ftbfs with GCC-7

[Ferenc Wágner]

Matthias Klose <doko at debian.org> writes:

> /bin/bash ../libtool  --tag=CXX   --mode=link g++  -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -O2 -DNDEBUG  -Wl,-z,relro -Wl,-z,now -o samlsign samlsign-samlsign.o ../saml/libsaml.la -lxerces-c -lxmltooling -llog4shib  
> libtool: link: g++ -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -O2 -DNDEBUG -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/samlsign samlsign-samlsign.o  ../saml/.libs/libsaml.so -lxerces-c -lxmltooling -llog4shib
> ../saml/.libs/libsaml.so: undefined reference to `virtual thunk to xmltooling::AbstractComplexElement::getOrderedChildren[abi:cxx11]() const'
> ../saml/.libs/libsaml.so: undefined reference to `virtual thunk to xmltooling::AbstractSimpleElement::getOrderedChildren[abi:cxx11]() const'
> collect2: error: ld returned 1 exit status
> Makefile:453: recipe for target 'samlsign' failed

Hi Matthias,

I strongly suspect that this bug (and #853659 as well) is not a genuine
GCC 7 build error, but the result of trying to link against an
XMLTooling library built with GCC 6.  Looks like there is a slight ABI
change between GCC 6 and GCC 7.  As such, there reports aren't really
useful.  How should we best handle this situation?
-- 
Regards,
Feri