From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] D-Link DWB-120M and BlueZ 2.14
Date: Sun, 30 Jan 2005 21:58:34 +0100 [thread overview]
Message-ID: <1107118714.8384.15.camel@pegasus> (raw)
In-Reply-To: <200501302046.ALU31339@ms12.netsolmail.com>
Hi Chris,
> >do a "make install DESTDIR=$PWD/x" and then check what it is in the
> >directory "x". Show us the result of a "find x".
>
> Okay so I did this:
> ./configure --enable-bcm203x
> make install DESTDIR=$PWD/x
>
> here's what's in x:
>
> x
> x/usr
> x/usr/sbin
> x/usr/sbin/hcid
> x/usr/sbin/hciattach
> x/usr/sbin/hciconfig
> x/usr/sbin/sdpd
> x/usr/share
> x/usr/share/man
> x/usr/share/man/man5
> x/usr/share/man/man5/hcid.conf.5
> x/usr/share/man/man8
> x/usr/share/man/man8/hcid.8
> x/usr/share/man/man8/hciattach.8
> x/usr/share/man/man8/hciconfig.8
> x/usr/share/man/man8/sdpd.8
> x/usr/share/man/man1
> x/usr/share/man/man1/hcitool.1
> x/usr/share/man/man1/l2ping.1
> x/usr/share/man/man1/sdptool.1
> x/usr/share/man/man1/ciptool.1
> x/usr/share/man/man1/rfcomm.1
> x/usr/share/man/man1/dund.1
> x/usr/share/man/man1/pand.1
> x/usr/share/man/man1/hidd.1
> x/usr/bin
> x/usr/bin/hcitool
> x/usr/bin/l2ping
> x/usr/bin/sdptool
> x/usr/bin/ciptool
> x/usr/bin/rfcomm
> x/usr/bin/dund
> x/usr/bin/pand
> x/usr/bin/hidd
> x/usr/bin/bluepin
> x/etc
> x/etc/bluetooth
> x/etc/bluetooth/hcid.conf
> x/etc/bluetooth/pin
> x/etc/bluetooth/rfcomm.conf
>
> That's it...? Thanks for your help.
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
Regards
Marcel
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-01-30 20:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-30 20:46 [Bluez-users] D-Link DWB-120M and BlueZ 2.14 Chris Taylor
2005-01-30 20:58 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-31 8:06 Chris Taylor
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=1107118714.8384.15.camel@pegasus \
--to=marcel@holtmann.org \
--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