From: Erwin Authried <eauth@softsys.co.at>
To: "bluez-users@lists.sourceforge.net" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Can't open PIN file /home/chenjiajing/bluez//etc/bluetooth/pin!
Date: Wed, 08 Mar 2006 17:38:00 +0100 [thread overview]
Message-ID: <1141835880.27904.68.camel@justakiss> (raw)
In-Reply-To: <f64f4e8a0603080810v740f51fejeab23a6b86751b0@mail.gmail.com>
Am Donnerstag, den 09.03.2006, 00:10 +0800 schrieb zhu yong:
> I use the cmd 'hcid', but find that hcid find the pin file from error
> directory.
> the /home/chenjiajing/bluez/ is my compile directory.
> How can I change to the correct directory of '/etc/bluetooth/pin'?
> info as follows:
> # ./hcid -n -f /etc/bluetooth/hcid.conf
> hcid[32]: Bluetooth HCI daemon
> hcid[32]: Can't open PIN
> file /home/chenjiajing/bluez//etc/bluetooth/pin. No suc
> h file or directory(2)
> hcid[33]: Can't init device hci0. Connection timed out(110)
>
you need to specify --prefix=\"\" for "configure" in bluez-utils and
bluez-libs for cross compiling.
-Erwin
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2006-03-08 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 16:10 [Bluez-users] Can't open PIN file /home/chenjiajing/bluez//etc/bluetooth/pin! zhu yong
2006-03-08 16:38 ` Erwin Authried [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=1141835880.27904.68.camel@justakiss \
--to=eauth@softsys.co.at \
--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;
as well as URLs for NNTP newsgroup(s).