Your message dated Sat, 09 Sep 2017 07:51:27 +0200
with message-id <87a824mnc0....@lant.ki.iif.hu>
and subject line Re: Bug#853598: opensaml2: ftbfs with GCC-7
has caused the Debian Bug report #853598,
regarding opensaml2: ftbfs with GCC-7
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
853598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853598
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:opensaml2
Version: 2.6.0-4
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/opensaml2_2.6.0-4_unstable_gcc7.log
The last lines of the build log are at the end of this report.
To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html
[...]
from /usr/include/xmltooling/XMLObjectBuilder.h:35,
from /usr/include/xmltooling/ConcreteXMLObjectBuilder.h:30,
from ../saml/saml2/core/Assertions.h:33,
from ../saml/saml2/metadata/Metadata.h:30,
from samlsign.cpp:39:
/usr/include/c++/7/bits/unique_ptr.h:51:28: note: declared here
template<typename> class auto_ptr;
^~~~~~~~
samlsign.cpp:316:21: warning: 'template<class> class std::auto_ptr' is
deprecated [-Wdeprecated-declarations]
auto_ptr<MetadataProvider> metadata(buildPlugin(m_param,
conf.MetadataProviderManager));
^~~~~~~~
In file included from /usr/include/c++/7/memory:80:0,
from /usr/include/xmltooling/XMLObjectBuilder.h:35,
from /usr/include/xmltooling/ConcreteXMLObjectBuilder.h:30,
from ../saml/saml2/core/Assertions.h:33,
from ../saml/saml2/metadata/Metadata.h:30,
from samlsign.cpp:39:
/usr/include/c++/7/bits/unique_ptr.h:51:28: note: declared here
template<typename> class auto_ptr;
^~~~~~~~
samlsign.cpp:354:13: warning: 'template<class> class std::auto_ptr' is
deprecated [-Wdeprecated-declarations]
auto_ptr<CredentialResolver> cr(
^~~~~~~~
In file included from /usr/include/c++/7/memory:80:0,
from /usr/include/xmltooling/XMLObjectBuilder.h:35,
from /usr/include/xmltooling/ConcreteXMLObjectBuilder.h:30,
from ../saml/saml2/core/Assertions.h:33,
from ../saml/saml2/metadata/Metadata.h:30,
from samlsign.cpp:39:
/usr/include/c++/7/bits/unique_ptr.h:51:28: note: declared here
template<typename> class auto_ptr;
^~~~~~~~
/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
make[3]: *** [samlsign] Error 1
make[3]: Leaving directory '/<<PKGBUILDDIR>>/samlsign'
Makefile:586: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
Makefile:492: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_build: make -j64 returned exit code 2
debian/rules:13: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
On Thu, 2 Feb 2017 13:28:24 +0100 Matthias Klose <d...@debian.org> wrote:
> On 02.02.2017 11:17, Ferenc Wágner wrote:
>
>> 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.
Since xmltooling_1.6.0-5 entered unstable, OpenSAML builds again.
Thus closing this.
--
Thanks,
Feri
--- End Message ---
