Bug 32673 - 0.13.10 fails to build with --enable-vala-bindings
Summary: 0.13.10 fails to build with --enable-vala-bindings
Status: RESOLVED NOTOURBUG
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-glib (show other bugs)
Version: git master
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
: 32705 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-12-26 18:50 UTC by Emilio Pozuelo Monfort
Modified: 2011-01-05 14:47 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Emilio Pozuelo Monfort 2010-12-26 18:50:01 UTC 
0.13.10 fails to build from source when configured with --enable-vala-bindings:

make[3]: Entering directory `/tmp/buildd/telepathy-glib-0.13.10/vala'
/usr/bin/vapigen \
		--library telepathy-glib \
		--pkg gio-2.0 \
		../telepathy-glib/TelepathyGLib-0.12.gir \
		
error: The type name `GLib.TypeInterface' could not be found
Generation failed: 1 error(s), 0 warning(s)
make[3]: *** [telepathy-glib.vapi] Error 1

I git bisected this and tracked it down to commit 86b80a0a351ba3d9a79a14a256c22b1191f7f4cc, which isn't buggy per se. I don't know whether this is tp-glib or something else's fault.
Comment 1 Simon McVittie 2011-01-03 04:03:39 UTC 
*** Bug 32705 has been marked as a duplicate of this bug. ***
Comment 2 Simon McVittie 2011-01-03 04:29:22 UTC 
I think it probably ought to be GObject.TypeInterface, but client-channel-factory's only mention of TypeInterface is "GTypeInterface parent;", so if this doesn't work, nobody else's GInterfaces will work either.

Which version of g-i and Vala are you using?
Comment 3 Emilio Pozuelo Monfort 2011-01-03 07:16:22 UTC 
I tried with g-i 0.9.12 and 0.10.0 and vala 0.10.1 (i.e. what is currently in Debian).
Comment 4 Emilio Pozuelo Monfort 2011-01-05 14:47:56 UTC 
Luca Bruno has fixed two bugs in the vala gir parser and says vala 0.11.3 should work fine.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.