From: Mika Linnanoja <mika.linnanoja@nokia.com>
To: ext Suraj Sumangala <Suraj.Sumangala@Atheros.com>
Cc: Eponymous - <the.epon@gmail.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: HCI data payload not getting through when using BlueZ
Date: Fri, 13 May 2011 11:26:54 +0300 [thread overview]
Message-ID: <4DCCEB4E.7040600@nokia.com> (raw)
In-Reply-To: <44EE5C37ADC36343B0625A05DD408C48517CE84134@CHEXMB-01.global.atheros.com>
On 05/13/2011 11:13 AM, ext Suraj Sumangala wrote:
> You have to enable it in the cofigure file and change "test_enable" from "no" to "yes".
> Edit the file "configure", search for "test_enable"
> change "test_enable=no" to "test_enable=yes"
>
> That is what I do to enable l2test. I guess there could be some other cleaner way to do it.
./configure --help :)
If you pull from the git repo ./bootstrap-configure already enables most of them.
Although lately configure is often *not* complaining if something is missing
from build dependencies, have to do a bit of trial & error to get it right.
This is very easy to notice when trying to 'make' bluez on a clean system
where it hasn't ever been built before.
Cheers,
Mika
next prev parent reply other threads:[~2011-05-13 8:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 8:52 HCI data payload not getting through when using BlueZ Eponymous -
2011-05-11 16:47 ` Gustavo F. Padovan
2011-05-12 10:19 ` Eponymous -
2011-05-13 7:54 ` Eponymous -
2011-05-13 8:13 ` Suraj Sumangala
2011-05-13 8:26 ` Mika Linnanoja [this message]
[not found] ` <BANLkTikJMKed11aRghia+7as9XGHokOH7w@mail.gmail.com>
[not found] ` <BANLkTi=H-iEn_oAMb1bwJk6KEAueHRMVtQ@mail.gmail.com>
2011-05-13 12:42 ` Fwd: " Eponymous -
2011-05-16 10:36 ` Eponymous -
2011-05-16 12:17 ` Anderson Lizardo
2011-05-17 7:13 ` Eponymous -
2011-05-17 11:50 ` Anderson Lizardo
2011-05-17 12:45 ` Eponymous -
[not found] ` <BANLkTinj5d0b+Gkz3QAWGCF_Vxc5UTTtrA@mail.gmail.com>
2011-05-24 8:12 ` Fwd: " Eponymous -
2011-05-30 13:57 ` Eponymous -
2011-06-03 17:35 ` Peter Hurley
2011-06-29 10:22 ` Eponymous -
2011-06-30 15:47 ` Peter Hurley
2011-07-01 6:46 ` Eponymous -
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=4DCCEB4E.7040600@nokia.com \
--to=mika.linnanoja@nokia.com \
--cc=Suraj.Sumangala@Atheros.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=the.epon@gmail.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;
as well as URLs for NNTP newsgroup(s).