From: Hasse Hagen Johansen <hhj@musikcheck.dk>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Troubles compiling btsco
Date: Tue, 23 Nov 2004 22:12:00 +0100 [thread overview]
Message-ID: <41A3A7A0.2040800@musikcheck.dk> (raw)
In-Reply-To: <41A3A32C.4090806@xmission.com>
Hi Brad
I'm using unstable(sid) so i'm not very happy to downgrade. But thanks
anyway ;-)
/Hasse
Brad Midgley wrote:
> Hasse,
>
> I know this isn't going to be a *lot* of help but I've been using
> debian with btsco. I don't know automake/autoconf/autobarf so I just
> update the various tools from -testing whenever they fail and it's
> working now...
>
> Brad
>
> Hasse Hagen Johansen wrote:
>
>> Hi
>>
>> I have checked out btsco from cvs from
>> http://www.gargan.org/linux/snd-bt-sco/
>>
>> tried to run the bootstrap but i failed because the automake(on my
>> debian sid) didn't include --ignore-deps but only had a include-deps
>> option. I removed that
>>
>> But when running configure I get this:
>>
>> ./configure: line 2919: XIPH_PATH_AO: command not found
>>
>> Don't know what that means, but it seems that this error is causing
>> some variable in the makefile not to substituted. I get this if I
>> then try to run make
>>
>> miyagi:/home/hhj/btsco# make
>> make all-recursive
>> make[1]: Entering directory `/home/hhj/btsco'
>> Making all in sbc
>> make[2]: Entering directory `/home/hhj/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/hhj/btsco/sbc'
>> make[1]: *** [all-recursive] Error 1
>> make[1]: Leaving directory `/home/hhj/btsco'
>> make: *** [all-recursive-am] Error 2
>>
>> I have tried to use a patch for debian from http://www.lxtreme.nl but
>> this doesn't seem to apply to the cvs version of btsco.
>>
>> Does anyone have some tips ffor compiling it on debian?
>>
>> Best Regards
>> Hasse H. Johansen
>>
>>
>>
>> -------------------------------------------------------
>> 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
>
>
>
> -------------------------------------------------------
> 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
-------------------------------------------------------
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-11-23 21:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 20:14 [Bluez-users] Troubles compiling btsco Hasse Hagen Johansen
2004-11-23 20:53 ` Brad Midgley
2004-11-23 21:12 ` Hasse Hagen Johansen [this message]
2004-11-23 21:05 ` Marcel Holtmann
2004-11-23 21:16 ` Hasse Hagen Johansen
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=41A3A7A0.2040800@musikcheck.dk \
--to=hhj@musikcheck.dk \
--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