From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] bluez-utils-2.17 -- Error compiling dbus.o
Date: Mon, 30 May 2005 14:39:42 +0200 [thread overview]
Message-ID: <1117456782.7072.141.camel@pegasus> (raw)
In-Reply-To: <e1effdeb0505300532fe36918@mail.gmail.com>
Hi Claudio,
> The DBUS is under development, the functions name/signatures changed.
> The bluez-utils 2.17 is compatible with D-Bus 0.23.
>
> I recommend use the D-Bus version 0.23. Change hcid and bluez-pin
> to support D-Bus 0.33 will require a signicant effort due bugs in the
> array iterator functions. I not sure if this problem was solved in the
> CVS version.
I never tested it against D-Bus 0.33, but it should be fixed.
The bluez-pin is another story, but I am not responsible for it.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-05-30 12:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-29 14:59 [Bluez-users] bluez-utils-2.17 -- Error compiling dbus.o Bruno Abinader
2005-05-29 15:11 ` Marcel Holtmann
2005-05-29 15:17 ` Bruno Abinader
2005-05-30 12:32 ` Claudio Takahasi
2005-05-30 12:39 ` Marcel Holtmann [this message]
2005-05-30 15:34 ` Bruno Abinader
2005-05-30 15:53 ` Marcel Holtmann
2005-05-31 20:41 ` Bruno Abinader
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1117456782.7072.141.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.