From: Marcel Holtmann <marcel@holtmann.org>
To: Pierre N <pierren@mac.com>
Cc: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] bluez-utils2: Bluetooth header files not found
Date: Fri, 23 Apr 2004 13:50:26 +0200 [thread overview]
Message-ID: <1082721025.1843.1.camel@merlin> (raw)
In-Reply-To: <1082711899.23022.10.camel@localhost>
Hi Pierre,
> 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?
you must not specify the path of the kernel includes, because userspace
programs should never include kernel header files. It is the prefix of
your previous installed libs2 from CVS.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-04-23 11:50 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
2004-04-23 12:57 ` Pierre N
2004-04-23 14:22 ` Marcel Holtmann
2004-04-23 11:50 ` Marcel Holtmann [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=1082721025.1843.1.camel@merlin \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=pierren@mac.com \
/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