GNOME Bugzilla – Bug 311563
dbus build fails if Pyrex is found but doesn't work.
Last modified: 2007-12-22 12:59:09 UTC
Version details: CVS 2005-07-25 Distribution/Version: SuSE 9.3 Building jhbuild fails on dbus if Pyrex isn't installed in the jhbuild path, but jhbuil doesn't install Pyrex. Once I'd manually installed Pyrex into the correct path, it worked fine. I was doing a tinderbox build, and the log for dbus is at http://home.rubberturnip.org.uk/jhbuild-logs/20050725-01/dbus.html
This looks like a bug in pyrex, not setting up its Python path correctly.
The latest dbus release specifically needs pyrex for python 2.4. I don't think there's a way to express that in a moduleset file...
If dbus requires a specific version of pyrex to compile its bindings, then it should check for that version at configure time (and either error out there, or turn off building of the bindings). Ending in an error part way through the build is a bug in dbus's build-foo. Adding Pyrex to the jhbuild build is not currently possible because I don't have the code in place for handling distutils modules (this is planned as part of a more general module type code refactor though). [ CC'ing John, since he works on the dbus python code ]
*** Bug 344460 has been marked as a duplicate of this bug. ***
Created attachment 69595 [details] [review] Fix the build, include pyrex
I went ahead and committed this patch in order to help prevent builds from failing, but it's worth noting that on IRC James said he was unsure of whether pyrex should appear in the bootstrap moduleset or in the freedesktop or gnome-2.16 one. So, I'll leave the bug open in case my choice turns out to be bad and we want to change it.
pyrex is no longer in any modulesets, I think this bug can be closed.
D-Bus Python Bindings 0.80.0 (24 January 2007) ============================================== - The "everything changes" release - Rewrite dbus_bindings (Pyrex) as _dbus_bindings (C) - API changes! - ... Pyrex is effectively no longer a dependency, marking bug as obsolete.