Source: k3d
Version: 0.8.0.2-19
Severity: serious
Tags: jessie sid

Hi,

k3d FTBFS on all architectures where it was binNMUed for the cgal
transition. From the amd64 build log:

[ 16%] Building CXX object 
k3dsdk/ngui/CMakeFiles/k3dsdk-ngui.dir/auto_property_page.cpp.o
cd /«PKGBUILDDIR»/obj-mips-linux-gnu/k3dsdk/ngui && /usr/bin/c++   
-DK3D_HAVE_EXPAT -DK3D_HAVE_SIGC_2_0 -Dk3dsdk_ngui_EXPORTS -g -O2 -Wformat 
-Werror=format-security -pipe -Wall -frounding-math -D_FORTIFY_SOURCE=2  -O2 -g 
-DNDEBUG -fPIC -I/«PKGBUILDDIR» -I/«PKGBUILDDIR»/k3dsdk/gil 
-I/«PKGBUILDDIR»/obj-mips-linux-gnu/k3dsdk -I/usr/include/glibmm-2.4 
-I/usr/lib/mips-linux-gnu/glibmm-2.4/include -I/usr/include/sigc++-2.0 
-I/usr/lib/mips-linux-gnu/sigc++-2.0/include -I/usr/include/glib-2.0 
-I/usr/lib/mips-linux-gnu/glib-2.0/include -I/usr/include/uuid 
-I/usr/include/giomm-2.4 -I/usr/lib/mips-linux-gnu/giomm-2.4/include 
-I/usr/include/gtk-2.0 -I/usr/include/gtk-unix-print-2.0 -I/usr/include/atk-1.0 
-I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng12 
-I/usr/lib/mips-linux-gnu/gtk-2.0/include -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/gio-unix-2.0 -I/usr/include/harfbuzz -I/usr/include/gtkmm-2.4 
-I/usr/lib/gtkmm-2.4/include -I/usr/include/atkmm-1.6 
-I/usr/include/pangomm-1.4 -I/usr/lib/pangomm-1.4/include 
-I/usr/include/gdkmm-2.4 -I/usr/lib/gdkmm-2.4/include 
-I/usr/include/cairomm-1.0 -I/usr/lib/cairomm-1.0/include    -o 
CMakeFiles/k3dsdk-ngui.dir/auto_property_page.cpp.o -c 
/«PKGBUILDDIR»/k3dsdk/ngui/auto_property_page.cpp
In file included from /«PKGBUILDDIR»/k3dsdk/ngui/auto_property_page.cpp:34:0:
/«PKGBUILDDIR»/k3dsdk/ngui/document_state.h:34:30: fatal error: 
gdk/gdkglcontext.h: No such file or directory
compilation terminated.

Full logs available via
https://buildd.debian.org/status/package.php?p=k3d

Regards,

Adam


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to