Bug#887775: libgnomekbd FTBFS: symbol differences

[Simon McVittie]

On Fri, 19 Jan 2018 at 22:35:01 +0200, Adrian Bunk wrote:
> - gkbd_indicator_VOID__VOID at Base 3.26.0
> +#MISSING: 3.26.0-2# gkbd_indicator_VOID__VOID at Base 3.26.0

> - gkbd_keyboard_drawing_VOID__UINT at Base 3.26.0
> +#MISSING: 3.26.0-2# gkbd_keyboard_drawing_VOID__UINT at Base 3.26.0

These are both "marshallers" generated by glib-genmarshal, and because
of their commonly-used type signatures they duplicate standard functions
provided by GLib itself (g_cclosure_marshal_VOID__VOID and
g_cclosure_marshal_VOID__UINT). When glib-genmarshal generates header
files, it makes those duplicate marshallers into a #define for the
ones in GLib.

Until recently, when glib-genmarshal generated function bodies, it
generated (unnecessary) bodies for these duplicates too; but now it
skips them.

This is *technically* an ABI break, but these functions aren't really
meant to be public ABI, a library user would have to go out of their
way (#undef the aliases for GLib functions) to call them, and codesearch
doesn't see any references. So I think they can be removed from the
symbols file or marked (optional).

    smcv