Bug#713594: mssh: FTBFS: pango-font.h:380:33: error: ISO C restricts enumerator values to range of 'int' [-Wpedantic]
Source: mssh
Version: 1.2-3
Severity: serious
Tags: jessie sid
User: debian-qa@lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm -I/usr/include/harfbuzz -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/vte-0.0 -D_FORTIFY_SOURCE=2 -pedantic-errors -Werror -Wall -Wfatal-errors -Wwrite-strings -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c mssh.c
> In file included from /usr/include/pango-1.0/pango/pango-attributes.h:25:0,
> from /usr/include/pango-1.0/pango/pango.h:25,
> from /usr/include/gtk-2.0/gdk/gdktypes.h:37,
> from /usr/include/gtk-2.0/gdk/gdkscreen.h:32,
> from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:31,
> from /usr/include/gtk-2.0/gdk/gdk.h:32,
> from /usr/include/gtk-2.0/gtk/gtk.h:32,
> from mssh.c:7:
> /usr/include/pango-1.0/pango/pango-font.h:380:33: error: ISO C restricts enumerator values to range of 'int' [-Wpedantic]
> PANGO_GLYPH_INVALID_INPUT = ((PangoGlyph)0xFFFFFFFF),
> ^
> compilation terminated due to -Wfatal-errors.
> make[3]: *** [mssh.o] Error 1
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/mssh_1.2-3_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
Reply to: