Bug#975429: inkscape: FTBFS against boost_1.74
Package: inkscape
Version: 1.0.1-1
Severity: important
Tags: ftbfs
User: team+boost@tracker.debian.org
Usertags: boost174
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Dear maintainer,
it was discovered that your package failed to build
against boost_1.74. Logs can be found here [1]. Most relevant
part is probably this:
[ 71%] Building CXX object src/CMakeFiles/inkscape_base.dir/ui/tool/selector.cpp.o
cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src && /usr/bin/c++ -DHAVE_CONFIG_H -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -DWITH_CSSBLEND -DWITH_CSSCOMPOSITE -DWITH_MESH -DWITH_SVG2 -Dinkscape_base_EXPORTS -I/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src -I/<<PKGBUILDDIR>>/src -I/<<PKGBUILDDIR>> -I/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/include -I/<<PKGBUILDDIR>>/src/3rdparty/adaptagrams -isystem /usr/include/pango-1.0 -isystem /usr/include/fribidi -isystem /usr/include/cairo -isystem /usr/include/pixman-1 -isystem /usr/include/harfbuzz -isystem /usr/include/uuid -isystem /usr/include/freetype2 -isystem /usr/include/libpng16 -isystem /usr/include/libsoup-2.4 -isystem /usr/include/libxml2 -isystem /usr/include/libmount -isystem /usr/include/blkid -isystem /usr/include/glib-2.0 -isystem /usr/lib/x86_64-linux-gnu/glib-2.0/include -isystem /usr/include/gc -isystem /usr/include/poppler -isystem /usr/include/libwpg-0.3 -isystem /usr/include/librevenge-0.0 -isystem /usr/include/libvisio-0.1 -isystem /usr/include/libcdr-0.1 -isystem /usr/include/dbus-1.0 -isystem /usr/lib/x86_64-linux-gnu/dbus-1.0/include -isystem /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/extension/dbus -isystem /usr/include/gtkmm-3.0 -isystem /usr/lib/x86_64-linux-gnu/gtkmm-3.0/include -isystem /usr/include/atkmm-1.6 -isystem /usr/include/gtk-3.0/unix-print -isystem /usr/include/gdkmm-3.0 -isystem /usr/lib/x86_64-linux-gnu/gdkmm-3.0/include -isystem /usr/include/giomm-2.4 -isystem /usr/lib/x86_64-linux-gnu/giomm-2.4/include -isystem /usr/include/pangomm-1.4 -isystem /usr/lib/x86_64-linux-gnu/pangomm-1.4/include -isystem /usr/include/glibmm-2.4 -isystem /usr/lib/x86_64-linux-gnu/glibmm-2.4/include -isystem /usr/include/cairomm-1.0 -isystem /usr/lib/x86_64-linux-gnu/cairomm-1.0/include -isystem /usr/include/sigc++-2.0 -isystem /usr/lib/x86_64-linux-gnu/sigc++-2.0/include -isystem /usr/include/libgdl-3.0 -isystem /usr/include/gtk-3.0 -isystem /usr/include/at-spi2-atk/2.0 -isystem /usr/include/at-spi-2.0 -isystem /usr/include/gio-unix-2.0 -isystem /usr/include/atk-1.0 -isystem /usr/include/gdk-pixbuf-2.0 -isystem /usr/include/gtkspell-3.0 -isystem /usr/include/enchant-2 -isystem /usr/include/x86_64-linux-gnu/ImageMagick-6 -isystem /usr/include/ImageMagick-6 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fstack-protector-strong -Werror=format -Werror=format-security -pthread -fopenmp -O3 -DNDEBUG -fPIC -pthread -fopenmp -fopenmp -fopenmp -fPIC -std=gnu++11 -o CMakeFiles/inkscape_base.dir/ui/tool/selector.cpp.o -c /<<PKGBUILDDIR>>/src/ui/tool/selector.cpp
/<<PKGBUILDDIR>>/src/ui/tool/node.cpp:100:25: error: field ‘rel_error’ has incomplete type ‘std::atomic<double>’
100 | std::atomic<double> rel_error; /// Cached relative error
It is planned to push boost_1.74 as the default version in Debian/Bullseye.
[1] http://qa-logs.debian.net/2020/10/27-boost/boost/inkscape_1.0.1-1_unstable_boost.log
Best regards
Anton
- -- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl+6H1sRHGdsYWRrQGRl
Ymlhbi5vcmcACgkQ0+Fzg8+n/wbDoQ/9FuEkHjHdg00XFomXpODUrIcSP5TCoq26
fbNuu0Ej1QpTke1qN4gwSY2MEf7xzlRDAZXtTBA7x1noGL+hx0eu+LTPAeNQ4Wgq
Ag4yAU8pE1MK1BQezJE9vuQaToW9aqLfPRpSTJQALbQpvmUCmb1iFMNkzRz6W53a
maNTvToez8dsT3Hy0a6v6XHkn9+KqT5+YNM8lmkxOI3dtU8XzPD0Mvc7P/QGsrhw
f9iufn5dr8LAJ0RA2HBM6LtnTWF3YxYq/Ebt9V9AdRmdGRtxaYrrRsMI8APNLZJ4
zSxB8FwTOKOwWGHybscRrioReVkzMuXs0bqJbtjXwE+eJCFsqChSKZYakADak38e
K7P+5EhKW577aCXUMbKlTnZ9jsmhepP09bOL/49Om8Bmpf10Rwx/4Ru4Su4ud9vO
iCQqGo9P3LBjlbSBxAiOJPsXIhBsjxvv/g7jvieyU1Fz4ZIzwYOAaH4LOJ8zBvr8
o50Q/IK3zc2up8MbWIvFBi2BxwIYn0jdfBwrkzhpqYb54n7fGZQrwPfbTwYh1Jxv
ye2jg9/Oo/NReuP8dlVmAq9WvA70LPq04NMfxYR5pEHJ0Hmwg85xlPGYDjAbtxSd
eGzBEtwOBLy2jN8CbP5XvzNn8yxXHLidOmxtQMcRNd6zf2uBFzdB31/SGmbaC2Nv
Fazxv0DgPOE=
=9tCo
-----END PGP SIGNATURE-----
Reply to: