dbus building pains



After bludgeoning jhbuild to get it to build the latest CVS checkouts, I
have reached a point I can't get past. The dbus developers on Freenode
can't seem to help either. An informal poll on #gnome-hackers says that
GNOME has been unbuildable for at least the past few days. Anyone who
can shed some light on this would be much appreciated.

make[2]: Entering directory `/home/jclinton/cvs/gnome2/dbus-glib/tools'
DBUS_TOP_BUILDDIR=.. dbus-send --system --print-reply=literal
--dest=org.freedesktop.DBus /org/freedesktop/DBus
org.freedesktop.DBus.Introspectable.Introspect >
dbus-bus-introspect.xml.tmp && mv dbus-bus-introspect.xml.tmp
dbus-bus-introspect.xml
Failed to open connection to system message bus: Failed to connect to
socket /home/jclinton/var/run/dbus/system_bus_socket: No such file or
directory
make[2]: *** [dbus-bus-introspect.xml] Error 1
make[2]: Leaving directory `/home/jclinton/cvs/gnome2/dbus-glib/tools'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/jclinton/cvs/gnome2/dbus-glib'
make: *** [all] Error 2

So apparently, dbus-glib is attempting to contact the dbus server built
in the previous module. Some googling came up with this build log:

http://home.rubberturnip.org.uk/jhbuild-logs/20050726-01/dbus.html

Which seems to imply that, at least at one point, the build attempted to
start a temporary instance of the dbus server.

Is this not the case now? Has anyone built GNOME in the past few days?

Attachment: signature.asc
Description: This is a digitally signed message part



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]