From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] [bluetooth-alsa] and [libao-devel]
Date: Mon, 13 Dec 2004 15:36:46 +0100 [thread overview]
Message-ID: <1102948606.8750.159.camel@pegasus> (raw)
In-Reply-To: <cpk3v3$4bb$1@sea.gmane.org>
Hi,
> If you are having troubles trying to install the bluetooth-alsa for
> headset support (http://bluetooth-alsa.sourceforge.net/) from a clean
> Fedora Core 3 installation, this may help you:
>
> Following the build instructions from the page above I got this output
> from the ./configure script:
> .
> .
> .
> > 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
> .
> .
> and the make process generates the following output+errors:
>
> make all-recursive
> make[1]: Entering directory `/home/lpeiro/btsco'
> Making all in sbc
> make[2]: Entering directory `/home/lpeiro/btsco/sbc'
> gcc -DHAVE_CONFIG_H -I. -I. -I.. @AO_CFLAGS@ -Wall -O2 -c sbclib.c
> gcc: @AO_CFLAGS@: No such file or directory
> make[2]: *** [sbclib.o] Error 1
> make[2]: Leaving directory `/home/lpeiro/btsco/sbc'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/lpeiro/btsco'
> make: *** [all] Error 2
>
>
> In order to have XIPH_PATH_AO available you will need libao-devel
> package installed. This can be found at www.rpmfind.net, for the fedora
> distribution.
> After that building process worked smoth for me.
we know and actually I already pointed this out in another thread you
can find in the mailing list archive ;)
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-12-13 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 13:02 [Bluez-users] [bluetooth-alsa] and [libao-devel] soraberri
2004-12-13 14:36 ` Marcel Holtmann [this message]
2004-12-13 15:20 ` [Bluez-users] " soraberri
2004-12-13 15:51 ` soraberri
2004-12-13 16:14 ` Sebastian Roth
2004-12-14 10:22 ` soraberri
2004-12-14 10:30 ` 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=1102948606.8750.159.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 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.