On Thu, Dec 26, 2013 at 08:15:29AM -0000, Alan Modra wrote: > I'm fairly certain this is a bug in the test itself.
> If you take a look at glib2.0/gobject/gmarshal.c > g_cclosure_marshal_VOID__PARAM, you see > typedef void (*GMarshalFunc_VOID__PARAM) (gpointer data1, > gpointer arg_1, > gpointer data2); > That says to me that all of the signal functions in gtk/tests/builder.c > should be declared as > signal_normal (GtkWindow *window, GParamSpec *spec) > not > signal_normal (GtkWindow *window, GParamSpec spec) > The "spec" parameter corresponds to "arg_1" in the typedef, which is a > pointer. Thanks Alan, confirmed here that fixing the prototypes of the signal functions resolves the testsuite failure. I'm uploading gtk+3.0 to Ubuntu now with this patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1262380 Title: gtk+3.0 FTBFS on ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1262380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
