From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Problems to compilate a code in Red Hat 9
Date: Fri, 30 Sep 2005 08:42:37 +0200 [thread overview]
Message-ID: <1128062557.4955.1.camel@localhost.localdomain> (raw)
In-Reply-To: <008901c5c523$ab190cc0$0300a8c0@akira>
Hi,
> One stupid question...=20
> =20
> I Try to compilate your example of bluetooth code but I have a
> problem:
> (I using Ret HAT 9 with blueZ, the module of bluetooth works perfect).
> =20
> Well when I try to compilate the coder with the GCC (make command),
> the GCC don=C2=B4t found the <bluetooth/bluetooth.h>
> =20
> Can you comment the correct configurate to compilate this?=20
> I am sure that the problem is for my configuration.
> =20
> (The BlueZ includes are in my machine
> in /usr/scr/linux-2.4.20-31.9/include/net/bluetooth)
we don't mix kernel headers with userspace headers. Get yourself the
bluez-libs development package and actually the latest 2.6 kernel would
also be a good idea.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-09-30 6:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 18:29 [Bluez-devel] Problems to compilate a code in Red Hat 9 Sir Graham
2005-09-30 6:42 ` Marcel Holtmann [this message]
2005-09-30 7:00 ` Sir Graham
2005-09-30 7:33 ` Marcel Holtmann
2005-09-30 8:09 ` Sir Graham
2005-09-30 8:15 ` Marcel Holtmann
2005-09-30 8:34 ` Sir Graham
2005-09-30 8:40 ` Bastien Nocera
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=1128062557.4955.1.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=bluez-devel@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