From wferi at niif.hu  Thu Feb  2 10:17:18 2017
From: wferi at niif.hu (Ferenc =?UTF-8?Q?W=C3=A1gner?=)
Date: Thu, 02 Feb 2017 11:17:18 +0100
Subject: Bug#853598: opensaml2: ftbfs with GCC-7
In-Reply-To: <E1cYUpt-0007cM-I0@paradis.debian.org> (Matthias Klose's message
 of "Tue, 31 Jan 2017 09:34:49 +0000")
References: <E1cYUpt-0007cM-I0@paradis.debian.org>
Message-ID: <87shnwzykx.fsf@lant.ki.iif.hu>

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


From doko at debian.org  Thu Feb  2 12:28:24 2017
From: doko at debian.org (Matthias Klose)
Date: Thu, 2 Feb 2017 13:28:24 +0100
Subject: Bug#853598: opensaml2: ftbfs with GCC-7
In-Reply-To: <87shnwzykx.fsf@lant.ki.iif.hu>
References: <E1cYUpt-0007cM-I0@paradis.debian.org>
 <87shnwzykx.fsf@lant.ki.iif.hu>
Message-ID: <04d2ac6f-acdd-e07e-6457-1dad637a2d57@debian.org>

On 02.02.2017 11:17, Ferenc W?gner wrote:
> 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
> 
> 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?

I would prefer to keep these open, clone the issue, and add a dependency once
the issue is analyzed. And it's easier not to file duplicates in follow-up test
rebuilds.

Matthias