On 8/18/20 1:24 PM, Ken Moffat via blfs-dev wrote:
I build inkscape on this machine, with the same set of flags that
I'm currently using, just under a week ago. But now on 10.0-rc1 it
fails:
cd /scratch/working/inkscape-1.0_2020-05-01_4035a4fb49/build/src &&
/usr/bin/c++ -DHAVE_CONFIG_H -DWITH_CSSBLEND -DWITH_CSSCOMPOSITE -DWITH_MESH
-DWITH_SVG2 -Dinkscape_base_EXPORTS
-I/scratch/working/inkscape-1.0_2020-05-01_4035a4fb49/build/src
-I/scratch/working/inkscape-1.0_2020-05-01_4035a4fb49/src
-I/scratch/working/inkscape-1.0_2020-05-01_4035a4fb49
-I/scratch/working/inkscape-1.0_2020-05-01_4035a4fb49/build/include
-I/scratch/working/inkscape-1.0_2020-05-01_4035a4fb49/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/uuid -isystem
/usr/include/freetype2 -isystem /usr/include/libpng16 -isystem /usr/include/harfbuzz
-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/glib-2.0/include -isystem /usr/include/gc -isystem
/usr/include/poppler -isystem /usr/include/gtkmm-3.0 -isystem
/usr/lib/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/gdkmm-3.0/include -isystem /usr/include/giomm-2.4 -isystem
/usr/lib/giomm-2.4/include -isystem /usr/include/pangomm-1.4 -isystem
/usr/lib/pangomm-1.4/include -isystem /usr/include/glibmm-2.4 -isystem
/usr/lib/glibmm-2.4/include -isystem /usr/include/cairomm-1.0 -isystem
/usr/lib/cairomm-1.0/include -isystem /usr/include/sigc++-2.0 -isystem
/usr/lib/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/dbus-1.0 -isystem
/usr/lib/dbus-1.0/include -isystem /usr/include/gio-unix-2.0 -isystem
/usr/include/libdrm -isystem /usr/include/atk-1.0 -isystem /usr/include/gdk-pixbuf-2.0
-O3 -march=native -fstack-clash-protection -D_FORTIFY_SOURCE=2 -fstack-protector-strong
-D_GLIBCXX_ASSERTIONS -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fstack-protector-strong
-Werror=format -Werror=format-security -pthread -fopenmp -O3 -DNDEBUG -fPIC -pthread
-fPIC -std=gnu++11 -o CMakeFiles/inkscape_base.dir/ui/tool/node.cpp.o -c
/scratch/working/inkscape-1.0_2020-05-01_4035a4fb49/src/ui/tool/node.cpp
/scratch/working/inkscape-1.0_2020-05-01_4035a4fb49/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
| ^~~~~~~~~
In file included from /usr/include/c++/10.2.0/bits/shared_ptr_atomic.h:33,
from /usr/include/c++/10.2.0/memory:85,
from
/scratch/working/inkscape-1.0_2020-05-01_4035a4fb49/src/preferences.h:21,
from
/scratch/working/inkscape-1.0_2020-05-01_4035a4fb49/src/desktop.h:33,
from
/scratch/working/inkscape-1.0_2020-05-01_4035a4fb49/src/ui/tool/node.cpp:19:
/usr/include/c++/10.2.0/bits/atomic_base.h:152:12: note: declaration of 'struct
std::atomic<double>'
152 | struct atomic;
| ^~~~~~
make[2]: *** [src/CMakeFiles/inkscape_base.dir/build.make:5120:
src/CMakeFiles/inkscape_base.dir/ui/tool/node.cpp.o] Error 1
Note the 'Cached relative error' comment.
After some random searches without any relevant results, I
eventually discovered that boost has a concept of a 'relative
error'.
But I'm guessing this might be the first time anybody has tried to
build inkscape with boost-1.74.0. No idea how to fix it.
ĸen
Hi Ken,
I have a fix in my sandbox right now rendering
You'll want to add "#include <atomic>" either above or below "#include
<iostream>". I've read conflicting reports about this regarding Boost,
glibc, and gcc. I was able to build it with Poppler before freeze, so I
know it's not that. I attributed it to glibc in my sandbox. This is the
sed I entered:
sed -i '/#include <iostream>/a #include <atomic>'
src/ui/tool/node.cpp
- Doug
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
