From: "Rolf S. Dubitzky " <Dubitzky@physi.uni-heidelberg.de>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Re: hcid crashing on pin_code_request
Date: Tue, 15 Nov 2005 10:22:05 +0100 [thread overview]
Message-ID: <200511151022.11133.Dubitzky@physi.uni-heidelberg.de> (raw)
In-Reply-To: <200511141913.48954.Dubitzky@physi.uni-heidelberg.de>
[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]
Hi,
I got it to work now. For completeness:
1) the bluez packages (see original post) in FedoraC4 are broken. They
don't work and crash in the way I posted.
=> get latest version and compile yourself
2) the current version of bluez-utils (2.22) doesn't compile propperly on
FC4. The ./configure doesn't find the dbus libraries and just doesn't
compile with dbus support, but without dbus support bluez is unusable for
me. I would concider this to be a bug in bluez, but ymmv.
Now without dbus support sdp doesn't work, e.g. sdptool browse just
returns
Failed to connect to SDP server on 00:07:A4:03:97:24: Connection timed
out
So if a tool doesn't work without dbus, I'd highly recommend to make dbus
a requirement, not an option.
The problem with compiling on FC4 is that for some funky reason dbus
headers are spread over two directories:
/usr/include/dbus-1.0/dbus/* (e.g. dbus.h)
and one other file in
/usr/lib/dbus-1.0/include/dbus/dbus-arch-deps.h
So you have to -I _both_ directories to make #include dbus/dbus.h compile.
Cheers, Rolf
[-- Attachment #2: Type: text/html, Size: 1492 bytes --]
prev parent reply other threads:[~2005-11-15 9:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 13:52 [Bluez-users] hcid crashing on pin_code_request Rolf S. Dubitzky
2005-11-14 16:05 ` [Bluez-users] " Rolf S. Dubitzky
2005-11-14 16:38 ` jimmi
2005-11-14 18:13 ` Rolf S. Dubitzky
2005-11-15 9:22 ` Rolf S. Dubitzky [this message]
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=200511151022.11133.Dubitzky@physi.uni-heidelberg.de \
--to=dubitzky@physi.uni-heidelberg.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox