From: Pierre N <pierren@mac.com>
To: Geoff Shang <gshang@pacific.net.au>
Cc: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] bluez-utils2: Bluetooth header files not found
Date: Fri, 23 Apr 2004 12:52:15 +0200 [thread overview]
Message-ID: <1082717535.24548.16.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.44.0404231939570.1728-100000@data.home>
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
Done. Got libs (and after that libs2) from CVS.
./bootstrap
./configure
Pointed --with-bluetooth to the proper path and now here is what I get:
checking bluetooth/bluetooth.h usability... yes
checking bluetooth/bluetooth.h presence... no
configure: WARNING: bluetooth/bluetooth.h: accepted by the compiler,
rejected by the preprocessor!
configure: WARNING: bluetooth/bluetooth.h: proceeding with the
compiler's result
checking for bluetooth/bluetooth.h... yes
checking for bt_inquiry in -lbluetooth... no
configure: error: Bluetooth library not found
Moving forward slowly...
--
Pierre
On Fri, 2004-04-23 at 11:40, Geoff Shang wrote:
> On Fri, 23 Apr 2004, Pierre N wrote:
>
> > 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
>
> Have you compiled and installed bluez-libs?
>
> Geoff.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-04-23 10:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 9:18 [Bluez-users] bluez-utils2: Bluetooth header files not found Pierre N
2004-04-23 9:40 ` Geoff Shang
2004-04-23 10:52 ` Pierre N [this message]
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=1082717535.24548.16.camel@localhost \
--to=pierren@mac.com \
--cc=bluez-users@lists.sourceforge.net \
--cc=gshang@pacific.net.au \
/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