Bug#701458: packages including glibconfig.h and building with GCC 4.8 -Werror ftbfs

[Matthias Klose]

Package: src:glib2.0
Version: 2.33.12+really2.32.4-5
Severity: important
Tags: sid jessie
User: debian-gcc at lists.debian.org
Usertags: ftbfs-gcc-4.8

packages including glibconfig.h and building with GCC 4.8 from experimental fail
to build from source.

In file included from /usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h:9:0,
                 from /usr/include/glib-2.0/glib/gtypes.h:34,
                 from /usr/include/glib-2.0/glib/galloca.h:34,
                 from /usr/include/glib-2.0/glib.h:32,
                 from /usr/include/glib-2.0/gobject/gbinding.h:30,
                 from /usr/include/glib-2.0/glib-object.h:25,
                 from byzanzencoder.h:20,
                 from byzanzencoder.c:24:
byzanzencoder.c: In function 'byzanz_encoder_get_type':
/usr/include/glib-2.0/glib/gmacros.h:162:53: error: typedef
'_GStaticAssertCompileTimeAssertion_0' locally defined but not used
[-Werror=unused-local-typedefs]
 #define G_STATIC_ASSERT(expr) typedef char G_PASTE
(_GStaticAssertCompileTimeAssertion_, __COUNTER__)[(expr) ? 1 : -1]

The packages which ftbfs are:

byzanz 0.3.0+git20120930-1
clutter-gesture 0.0.2.1-7
darktable 1.1.3-1
drivel 3.0.3-1
gcompris 12.01-1
geoclue 0.12.0-4
gitg 0.2.4-1.1
gnurobots 2:1.2.0-4
gtkimageview 1.6.4+dfsg-0.1
ido 0.3.4-1
indicator-application 0.5.0-1
indicator-messages 0.6.0-1
indicator-session 0.3.96-1
libappindicator 0.4.92-2
libdbusmenu 0.6.2-1
libindicate 0.6.92-1
libindicator 0.5.0-1
link-monitor-applet 3.0-8
mail-notification 5.4.dfsg.1-6
modemmanager 0.5.2.0-2
mssh 1.2-2
muffin 1.1.2-1
mydumper 0.5.1-3
network-manager-iodine 0.0.4-1
network-manager-openconnect 0.9.4.0-8
network-manager-openvpn 0.9.4.0-1
network-manager-pptp 0.9.4.0-2
network-manager-strongswan 1.3.0-1
network-manager-vpnc 0.9.4.0-1

build logs at http://people.debian.org/~doko/logs-20130217/gcc48/

would it possible to provide a build of the package with the installed header
fixed for a follow-up test rebuild?