From: "Mumia W.." <paduille.4061.mumia.w+nospam@earthlink.net>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] compile error: bluetooth/bluetooth.h: No such file or directory
Date: Sat, 26 Jul 2008 19:32:51 -0500 [thread overview]
Message-ID: <488BC233.8070905@earthlink.net> (raw)
In-Reply-To: <BLU117-W424BD43283F81BA6D5CF67DF810@phx.gbl>
On 07/26/2008 04:35 PM, thanit sara wrote:
> [...] $ gcc -g -o simplescan simplescan.c -lblutooth "
> As result, below is what I got.
>
> simplescan.c:5:33: error: bluetooth/bluetooth.h: No such file or directory
> simplescan.c:6:27: error: bluetooth/hci.h: No such file or directory
> simplescan.c:7:31: error: bluetooth/hci_lib.h: No such file or directory
> [...]
It looks like you need the development packages for bluetooth installed.
For Debian Etch, libbluetooth2-dev contains these files. No doubt it
will be slightly different for Fedora.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2008-07-27 0:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 10:36 [Bluez-users] #define OGF_TESTING_CMD potentially wrong? Peter Wurmsdobler
2008-07-22 12:45 ` Marcel Holtmann
2008-07-22 13:41 ` Peter Wurmsdobler
2008-07-26 21:35 ` [Bluez-users] compile error: bluetooth/bluetooth.h: No such file or directory thanit sara
2008-07-27 0:32 ` Mumia W.. [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=488BC233.8070905@earthlink.net \
--to=paduille.4061.mumia.w+nospam@earthlink.net \
--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