From: Bob Gustafson <bobgus@rcn.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] btsco under FC3
Date: Thu, 6 Jan 2005 01:28:17 -0600 [thread overview]
Message-ID: <v04020a17be02951102ed@[192.168.49.19]> (raw)
In-Reply-To: <5256d0b05010520461ad68ff3@mail.gmail.com>
Hi
I got the same thing and managed to fix it by hacking the Makefile in the
sbc directory.
replace the @AO.. stuff in the LDFLAGS with
LDFLAGS = -lao
replace the other place the @AO occurs with nothing (I don't see where at
the moment)
add in libtool commands in the COMPILE and LINK lines - see below
[root@hoho2 btsco]# cd sbc
[root@hoho2 sbc]# grep libtool Makefile
COMPILE = libtool --mode=compile $(CC) $(DEFS) $(DEFAULT_INCLUDES)
$(INCLUDES) $
(AM_CPPFLAGS) \
LINK = libtool --mode=link $(CCLD) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS)
$(LDFLAG
S) -o $@
[root@hoho2 sbc]#
I apologize for the crude instructions - I will send a patch for that
Makefile tomorrow. Actually, that is the wrong place to apply the patch,
but it seemed to work for me. (I have the btsco command working and it
seems to put out the correct text lines, but my HBH-65 headset isn't
talking at the moment. I tried the arecord and got a 44 byte wav file -
both times I tried.
BobG
On Thu, 6 Jan 2005 12:46:02 +0800 Peter Robinson <pbrobinson@gmail.com> wrote
>Hey All,
>
>Just trying to compile btsco under FC3 and have run into a little
>trouble compiling the latest CVS version. I can't actually get it to
>compile as yet but will include the HW details FYI.
>
>D-Link DBT-120 rev B2
>Headset Motorola HS-810
>I also have a Motorola HS-850 on the way (the 810 is actually a friends).
>
>The actual problem is that it can't locate the @AO_CFLAGS@ directory
>during compile. I'm following the directions on the website.
>
>Cheers
>Pete
>
>hciconfig hci0 revision
>hci0: Type: USB
> BD Address: 00:80:C8:26:F7:76 ACL MTU: 192:8 SCO MTU: 64:8
> HCI 15.3
> Chip version: BlueCore02
> Max key size: 56 bit
> SCO mapping: HCI
>[root@trinity ~]# lsusb
>Bus 001 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle
>
>[peter@trinity btsco]$ ./configure
>checking for a BSD-compatible install... /usr/bin/install -c
>checking whether build environment is sane... yes
>checking for gawk... gawk
>checking whether make sets $(MAKE)... yes
>checking for gcc... gcc
>checking for C compiler default output file name... a.out
>checking whether the C compiler works... yes
>checking whether we are cross compiling... no
>checking for suffix of executables...
>checking for suffix of object files... o
>checking whether we are using the GNU C compiler... yes
>checking whether gcc accepts -g... yes
>checking for gcc option to accept ANSI C... none needed
>checking for style of include used by make... GNU
>checking dependency style of gcc... none
>checking for a BSD-compatible install... /usr/bin/install -c
>checking for ranlib... ranlib
>checking for ALSA CFLAGS...
>checking for ALSA LDFLAGS... -lasound -lm -ldl -lpthread
>checking for libasound headers version >= 1.0.3... found.
>checking for snd_ctl_open in -lasound... yes
>./configure: line 3249: XIPH_PATH_AO: command not found
>configure: creating ./config.status
>config.status: creating Makefile
>config.status: creating sbc/Makefile
>config.status: creating avdtp/Makefile
>config.status: creating config.h
>config.status: config.h is unchanged
>config.status: executing depfiles commands
>[peter@trinity btsco]$ make
>make all-recursive
>make[1]: Entering directory `/home/peter/download/voip/btsco'
>Making all in sbc
>make[2]: Entering directory `/home/peter/download/voip/btsco/sbc'
>rm -f libsbc.a
>ar cru libsbc.a sbc.o
>ranlib libsbc.a
>gcc -DHAVE_CONFIG_H -I. -I. -I.. @AO_CFLAGS@ -Wall -O2 -c sbcinfo.c
>gcc: @AO_CFLAGS@: No such file or directory
>make[2]: *** [sbcinfo.o] Error 1
>make[2]: Leaving directory `/home/peter/download/voip/btsco/sbc'
>make[1]: *** [all-recursive] Error 1
>make[1]: Leaving directory `/home/peter/download/voip/btsco'
>make: *** [all] Error 2
>[peter@trinity btsco]$
>
>
>-------------------------------------------------------
>The SF.Net email is sponsored by: Beat the post-holiday blues
>Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
>It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
>_______________________________________________
>Bluez-devel mailing list
>Bluez-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bluez-devel
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-01-06 7:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 4:46 [Bluez-devel] btsco under FC3 Peter Robinson
2005-01-06 7:28 ` Bob Gustafson [this message]
2005-01-06 12:24 ` Marcel Holtmann
2005-01-06 14:23 ` Bob Gustafson
2005-01-06 14:51 ` Marcel Holtmann
2005-01-06 15:33 ` Bob Gustafson
2005-01-07 6:15 ` Peter Robinson
2005-01-07 7:14 ` Brad Midgley
2005-01-07 7:19 ` Peter Robinson
2005-01-07 11:08 ` Lars Grunewaldt
2005-01-07 11:01 ` Henryk Plötz
2005-01-07 11:10 ` Lars Grunewaldt
2005-01-08 1:42 ` Peter Robinson
-- strict thread matches above, loose matches on Subject: below --
2005-01-06 15:36 Bob Gustafson
2005-01-06 15:51 Bob Gustafson
2005-01-06 17:26 ` Marcel Holtmann
2005-01-07 3:30 ` Peter Robinson
2005-01-07 4:20 ` Brad Midgley
2005-01-07 3:43 ` Bob Gustafson
[not found] ` <v04020a21be03b42174eb@192.168.49.19>
2005-01-07 6:06 ` Peter Robinson
2005-01-06 16:21 Bob Gustafson
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='v04020a17be02951102ed@[192.168.49.19]' \
--to=bobgus@rcn.com \
--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