From: Brad Midgley <bmidgley@xmission.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] btsco.41 and config.log does not give a ko file
Date: Thu, 12 Jan 2006 10:16:31 -0700 [thread overview]
Message-ID: <43C68EEF.4070801@xmission.com> (raw)
In-Reply-To: <43C675A7.1040308@pagestation.com>
Jerry
> I just downloaded btsco.41 did the ./configure; make; make install
> I have no ko file in the the btsco.41 directory.
>
> I had a problem where it could not find ao.h. I fixed that with "up2date
> libao-devel".
> I am using centos 4.2 which is compatible with RHEL 4.2.
the libao thing shouldn't have caused problems. I guess --disable-aotest
should have been specified when you didn't have the package
cd to the directory "kernel" and run make there to get the kernel
modules (just checked the docs; it's build step #4 on
http://bluetooth-alsa.sourceforge.net/ )
brad
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-01-12 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 15:28 [Bluez-users] btsco.41 and config.log does not give a ko file Jerry Geis
2006-01-12 17:16 ` Brad Midgley [this message]
2006-01-12 17:24 ` Jerry Geis
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=43C68EEF.4070801@xmission.com \
--to=bmidgley@xmission.com \
--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;
as well as URLs for NNTP newsgroup(s).