Build changes for 0.61

[Matt Hoosier]

I've run into the same problem in a Scratchbox non-x86 environment.
The trouble seems to be an incomplete implementation of UNIX sockets
(the default mode in which the bus fires up) in QEMU (used for CPU
transparency).

Patching the system bus's service configuration file ("system.xml"
perhaps? I don't have access to the source) to use TCP sockets instead
allowed my build to complete. You can always switch back to UNIX
sockets when deploying the build binaries onto the target system.

On 6/5/06, John (J5) Palmieri <johnp at redhat.com> wrote:
> Hello,
>
> Sorry for being late with the reply.  I've been busy lately.  The xml
> file is a stub for generating a convenience library for calling bus
> methods like ListNames.  It is not needed but you would have to fix the
> build to not try to generate those files.
>
> However, I realized the cause of the issue may be the Scratchbox
> environment.  What shell does it give you?  Right now the build assumes
> bash but if you use another shell that does not support bash syntax it
> may be that the bus is not exporting its address correctly when it is
> started by the build.  It is just a guess but worth looking into.
>
> On Wed, 2006-05-24 at 19:38 -0700, Diane Holt wrote:
> > Hi John,
> >
> > Thanks for the quick reply. But I'm not sure I fully understand it. Are
> > you saying nothing currently actually needs the .xml file? Can I simply
> > modify my tools/Makefile.am to not list it in the dependencies for
> > dbus-glib-bindings.h (and take the dbus-bus-introspect.xml target out)?
> > Will dbus-glib-bindings.h still get built correctly if I do?
> >
> > The reason I'm wanting to not have the launch/send get done is because
> > I'm trying to build dbus for ARM, in a Scratchbox environment, and while
> > it works for the x86 build, it doesn't for the ARM. Not sure why it
> > fails -- the daemon launches -- I can see it in my process table, but
> > the connection fails, maybe due to the daemon actually running via the
> > qemu-arm emulation? I was just going to source-control the .xml file and
> > remove the target for it -- but if I can simply remove the dependency
> > altogether, even better.
> >
> > Thanks!
> > Diane
> >
> > -----Original Message-----
> > From: John (J5) Palmieri [mailto:johnp at redhat.com]
> > Sent: Wednesday, May 24, 2006 6:10 PM
> > To: Diane Holt
> > Cc: dbus at lists.freedesktop.org
> > Subject: Re: Build changes for 0.61
> >
> > Hello diane,
> >
> > dbus-bus-introspect.xml is just a stub file for the glib bindings.  From
> > it we generate bindings to the bus methods such as AquireName and
> > ListNames, etc.  In reality we could just do this at dist time or even
> > take it out altogether because the bindings just give an added layer of
> > convenience when talking to the bus.  I'm not sure anyone actually uses
> > them and if they did it is easy enough to move to pure dbus calls
> > anyway
> >
> > On Wed, 2006-05-24 at 17:13 -0700, Diane Holt wrote:
> > > In the build process for 0.61, dbus is launched and a dbus-send is
> > > then done. It looks to be getting done for the generation of
> > > dbus-bus-introspect.xml, but I don't see what this file is actually
> > > used for - I don't see it getting installed anywhere. Is this file
> > > actually needed by something, and if so, is it something that's
> > > essential to the building of dbus, or can whatever needs it be
> > > disabled?
> >
> >
> >
> >
> >
> --
>
> _______________________________________________
> dbus mailing list
> dbus at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dbus
>