Linux bluetooth development
 help / color / mirror / Atom feed
From: Chris Taylor <cht@imipolex-g.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] D-Link DWB-120M and BlueZ 2.14
Date: Mon, 31 Jan 2005 00:06:24 -0800	[thread overview]
Message-ID: <200501310806.ALV29436@ms12.netsolmail.com> (raw)


>this can only mean that the libusb developer package is not installed.
>Check when you call configure for something like:
>
>checking usb.h usability... yes
>checking usb.h presence... yes
>checking for usb.h... yes
>checking for usb_open in -lusb... yes
>checking for usb_get_busses in -lusb... yes
>checking for usb_interrupt_read in -lusb... yes

Aha! I installed the libusb developer package and the firmware utility 
installed and it work fine now! Thanks for your help.


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2005-01-31  8:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-31  8:06 Chris Taylor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-30 20:46 [Bluez-users] D-Link DWB-120M and BlueZ 2.14 Chris Taylor
2005-01-30 20:58 ` Marcel Holtmann
2005-01-30 19:48 Chris Taylor
2005-01-30 19:52 ` Marcel Holtmann
2005-01-29  2:31 Chris Taylor
2005-01-29  1:28 Chris Taylor
2005-01-29  1:36 ` Marcel Holtmann
2005-01-28 21:51 Chris Taylor
2005-01-29  1:13 ` 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=200501310806.ALV29436@ms12.netsolmail.com \
    --to=cht@imipolex-g.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