From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] hcitool scan returns wrong bdaddr
Date: Mon, 26 Nov 2007 13:27:23 +0100 [thread overview]
Message-ID: <1196080043.17196.4.camel@aeonflux> (raw)
In-Reply-To: <474AA430.6010307@uni-koeln.de>
Hi Paul,
> thanks a lot for your fast resonse.
> I have installed dbus on my System so I assumed that bluez would use it.
> Is this wrong?
> I tried to find a archive for 3.21, but found none.
> So I load the CVS Version by:
>
> cvs -d:pserver:anonymous@cvs.bluez.org:/cvsroot/bluez login
> cvs -d:pserver:anonymous@cvs.bluez.org:/cvsroot/bluez co -P libs
>
>
> for some reason autoconf -o configure configure.in on my embedded box
> didn't create anything, so I ran it on my PC, copyed the resulting
> configure script to the box, and run bootstrap and bootstrap-configure.
> make and make install, produced /usr/lib/libbluetooth.so.2.9.2
use the bootstrap-configure and make sure it gets installed in /usr
prefix to make it available. The tarball is at the same location as the
3.22 version, but only one version earlier.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-11-26 12:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 19:35 [Bluez-users] hcitool scan returns wrong bdaddr Paul Wachendorf
2007-11-25 22:44 ` Paul Wachendorf
2007-11-26 5:38 ` Marcel Holtmann
2007-11-26 10:47 ` Paul Wachendorf
2007-11-26 12:27 ` Marcel Holtmann [this message]
2007-11-26 18:31 ` Paul Wachendorf
2007-11-29 7:43 ` Dave Young
2007-11-29 20:19 ` Marcel Holtmann
2007-11-30 2:52 ` Dave Young
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=1196080043.17196.4.camel@aeonflux \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.