Unable to build 0.2.12, error in module/gapplaunchhandlerzeitgeist.c

Bug #683805 reported by Linus Sjögren
34
This bug affects 6 people
Affects Status Importance Assigned to Milestone
libzeitgeist
Fix Released
Medium
Mikkel Kamstrup Erlandsen

Bug Description

Hey!

I'm trying to build libzeitgeist 0.2.12 with the sources from Launchpad, but I get an error in the module directory:

Making all in module
make[2]: Entering directory `/tmp/libzeitgeist-0.2.12/module'
  CC libgiozeitgeist_la-gapplaunchhandlerzeitgeist.lo
gapplaunchhandlerzeitgeist.c:37:74: error: expected ')' before '*' token
gapplaunchhandlerzeitgeist.c: In function 'g_app_launch_handler_zeitgeist_register_type':
gapplaunchhandlerzeitgeist.c:48:1: error: 'launch_handler_iface_init' undeclared (first use in this function)
gapplaunchhandlerzeitgeist.c:48:1: note: each undeclared identifier is reported only once for each function it appears in
gapplaunchhandlerzeitgeist.c:48:1: error: 'G_TYPE_DESKTOP_APP_INFO_LAUNCH_HANDLER' undeclared (first use in this function)
gapplaunchhandlerzeitgeist.c: At top level:
gapplaunchhandlerzeitgeist.c:227:43: error: expected ')' before '*' token
gapplaunchhandlerzeitgeist.c:284:62: error: expected ')' before '*' token
gapplaunchhandlerzeitgeist.c: In function 'g_app_launch_handler_zeitgeist_register':
gapplaunchhandlerzeitgeist.c:293:35: error: 'G_DESKTOP_APP_INFO_LAUNCH_HANDLER_EXTENSION_POINT_NAME' undeclared (first use in this function)
make[2]: *** [libgiozeitgeist_la-gapplaunchhandlerzeitgeist.lo] Error 1
make[2]: Leaving directory `/tmp/libzeitgeist-0.2.12/module'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/libzeitgeist-0.2.12'
make: *** [all] Error 2

I built using the following commands, in order:

./autogen.sh --prefix=/usr
make

My uname -a:

Linux flandre 2.6.36-ARCH #1 SMP PREEMPT Wed Nov 24 00:39:57 CET 2010 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 6400+ AuthenticAMD GNU/Linux

Revision history for this message
deanm (cubeist) wrote :

add this to your ./autogen.sh line:
--enable-module=no

Revision history for this message
Linus Sjögren (thelinx-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :

Thanks, now it builds.

Revision history for this message
Mikkel Kamstrup Erlandsen (kamstrup) wrote :

Yeah, this is a regrettable situation. Let me quickly outline why it is like it is.

For Unity we wanted to track "most popular" and "most recent" applications through Zeitgeist. This is not trivially doable for a number of reasons that I shall spare you, but we ended up writing a patch for GIO that can be found here https://bugzilla.gnome.org/show_bug.cgi?id=606960.

The patch breaks adds some new ABI and API to GIO by adding a new extension point that triggers a callback whenever an app is launched via GIO. The libzeitgeist sources contains a GIO module that requires the new extension point, but it does not properly detect whether the GIO headers are patched and by default assumes it is there (which is probably not ideal).

So that's the story.

Unless the GIO patch get accepted upstream I'll probably make --enable-module=no the default and then tell the Ubuntu packagers to build libzeitgeist with --enable-module=yes.

Changed in libzeitgeist:
assignee: nobody → Mikkel Kamstrup Erlandsen (kamstrup)
importance: Undecided → Medium
milestone: none → 0.3.0
status: New → Triaged
Revision history for this message
Michal Hruby (mhr3) wrote :

This was fixed in 0.3.4.

Changed in libzeitgeist:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.