From: Bastien Nocera <hadess@hadess.net>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: GCC-4 Patch for btsco
Date: Fri, 17 Jun 2005 11:33:39 +0000 (UTC) [thread overview]
Message-ID: <loom.20050617T133130-516@post.gmane.org> (raw)
In-Reply-To: 1119006318.8980.126.camel@pegasus
Marcel Holtmann <marcel <at> holtmann.org> writes:
> the bug was also present in the function itself. I have no idea how it
> slipped into the source. I fixed it with the bluez-libs-2.11 release.
Excellent, here's a patch to btsco to require bluez-libs 2.11.
$ ./configure
<snip
checking for hci_open_dev in -lbluetooth... yes
checking for sdp_connect in -lbluetooth... yes
configure: error: bluez-libs 2.11 or better is required to compile btsco
make: *** [config.status] Error 1
$ grep hci_switch_role config.log
conftest.c:35: error: incompatible type for argument 2 of 'hci_switch_role'
| hci_switch_role(dd, addr, role, to);
Index: configure.in
===================================================================
RCS file: /cvsroot/bluetooth-alsa/btsco/configure.in,v
retrieving revision 1.8
diff -u -r1.8 configure.in
--- configure.in 22 Apr 2005 17:17:25 -0000 1.8
+++ configure.in 17 Jun 2005 11:36:39 -0000
@@ -19,6 +19,22 @@
AC_PROG_RANLIB
AC_PATH_BLUEZ
+AC_TRY_COMPILE([
+ #include <bluetooth/bluetooth.h>
+ #include <sys/socket.h>
+ #include <bluetooth/hci.h>
+ #include <bluetooth/hci_lib.h>
+ ],[
+ bdaddr_t *addr;
+ int dd = 0;
+ int role = 0;
+ int to = 0;
+ hci_switch_role(dd, addr, role, to);
+ ],HAVE_BLUEZ=yes,HAVE_BLUEZ=no)
+if test x$HAVE_BLUEZ != xyes; then
+ AC_MSG_ERROR(bluez-libs 2.11 or better is required to compile btsco)
+fi
+
AM_PATH_ALSA(1.0.3)
XIPH_PATH_AO
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-06-17 11:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-17 10:05 [Bluez-devel] GCC-4 Patch for btsco Bastien Nocera
2005-06-17 10:23 ` Marcel Holtmann
2005-06-17 10:51 ` [Bluez-devel] " Bastien Nocera
2005-06-17 11:05 ` Marcel Holtmann
2005-06-17 11:33 ` Bastien Nocera [this message]
2005-06-17 13:31 ` Brad Midgley
2005-06-17 20:11 ` Bastien Nocera
2005-06-17 20:49 ` Brad Midgley
2005-06-17 21:26 ` Bastien Nocera
2005-06-17 18:45 ` Brad Midgley
2005-06-17 18:49 ` Luiz Fernando Capitulino
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=loom.20050617T133130-516@post.gmane.org \
--to=hadess@hadess.net \
--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