From: Bob Gustafson <bobgus@rcn.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] btsco under FC3
Date: Thu, 6 Jan 2005 08:23:44 -0600 [thread overview]
Message-ID: <v04020a19be02f88660fa@[192.168.49.19]> (raw)
In-Reply-To: <1105014278.4299.19.camel@pegasus>
Yes, I did that too.
something like 'up2date libao-devel', but the @AO. symbols were still in
the Makefile. I did lots of things, so need to do a clean install and
update to make certain what needs to be done to what.
It seemed as though all of the libao files installed in /usr/lib were of
the shared variety - thus I experimented with the libtool insertions in
sbc/Makefile as mentioned in my last email.
BobG
On Thu, 06 Jan 2005 13:24:38 +0100, Marcel Holtmann wrote:
>Hi Pete,
>
>> 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.
>
>what about installing the AO library development package.
>
>Regards
>
>Marcel
>
>
>
>
>-------------------------------------------------------
>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 14:23 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
2005-01-06 12:24 ` Marcel Holtmann
2005-01-06 14:23 ` Bob Gustafson [this message]
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='v04020a19be02f88660fa@[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