From: Pierre N <pierren@mac.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] bluez-utils2: Bluetooth header files not found
Date: Fri, 23 Apr 2004 11:18:19 +0200 [thread overview]
Message-ID: <1082711899.23022.10.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
Hi,
Trying to compile bluez-utils2 out from CVS. I get this error message on
./configure:
checking for unistd.h... yes
checking bluetooth/bluetooth.h usability... no
checking bluetooth/bluetooth.h presence... no
checking for bluetooth/bluetooth.h... no
configure: error: Bluetooth header files not found
I tried ./configure --without-bluetooth
./configure --with-bluetooth=/usr/src/kernel-headers-2.4.22 I always get
the same error message.
Using 2.4.22 on powerpc. What else do you guys need?
--
Pierre
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-04-23 9:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 9:18 Pierre N [this message]
2004-04-23 9:40 ` [Bluez-users] bluez-utils2: Bluetooth header files not found Geoff Shang
2004-04-23 10:52 ` Pierre N
2004-04-23 12:57 ` Pierre N
2004-04-23 14:22 ` Marcel Holtmann
2004-04-23 11:50 ` Marcel Holtmann
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=1082711899.23022.10.camel@localhost \
--to=pierren@mac.com \
--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