GNOME Bugzilla – Bug 656163
Gio-2.0.gir:47771.7-47775.24: error: `UnixSocketAddress' already contains a definition for `abstract'
Last modified: 2018-05-24 13:17:19 UTC
(Sorry if glib/gio is not the right reporting point, but gio-2.0.c in gobject-introspection seems to be generated off this source) While building libchamplain with gobject-introspection 1.29.16, the following build error appears: Gio-2.0.gir:47771.7-47775.24: error: `UnixSocketAddress' already contains a definition for `abstract' Gio-2.0.gir:47651.7-47653.103: note: previous definition of `abstract' was here The two definitions seem to come from those parts in gio-2.0.c: /** * GUnixSocketAddress:abstract: * * Whether or not this is an abstract address * distinguishes between zero-padded and non-zero-padded * abstract addresses. * * Deprecated: Use #GUnixSocketAddress:address-type, which */ /** * g_unix_socket_address_new_abstract: * @path: (array length=path_len) (element-type gchar): the abstract name * @path_len: the length of @path, or -1 * * Creates a new %G_UNIX_SOCKET_ADDRESS_ABSTRACT_PADDED * #GUnixSocketAddress for @path. * * Returns: a new #GUnixSocketAddress * Deprecated: Use g_unix_socket_address_new_with_type(). */ (There is a high chance I completely mis-understood all of this...the only fact is the build error above)
I can confirm this error. public int main (string[] argv) { stdout.printf ("Hello World!\n"); return 0; } Compile this code with 'valac --pkg Gio-2.0' or 'valac --pkg Gtk-3.0' valac will fail with: (valac:10946): GLib-CRITICAL **: g_str_has_suffix: assertion `str != NULL' failed ** (valac:10946): CRITICAL **: vala_gir_parser_node_lookup: assertion `name != NULL' failed Gio-2.0.gir:53587.7-53591.24: error: `UnixSocketAddress' already contains a definition for `abstract' Gio-2.0.gir:53459.7-53461.103: note: previous definition of `abstract' was here Compilation failed: 1 error(s), 0 warning(s)
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib/issues/437.