From: Mark Watson <mark@volantis.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Building btsco for Fedora 3
Date: Sun, 15 May 2005 01:47:37 +0100 [thread overview]
Message-ID: <42869C29.3040001@volantis.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 909 bytes --]
Hi. Hopefully this is the right list for this question.
I'm attempting to build btsco and the associated kernel driver for
Fedora 3, kernel 2.6.11-1.14_FC3
With btsco, I get ...
> make[2]: Entering directory `/tmp/btsco'
> gcc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/include -Wall -O2 -c a2recv.c
> a2recv.c: In function `make_master':
> a2recv.c:281: error: incompatible type for argument 2 of `hci_switch_role'
So, first question, can I get away with commenting out the relevant call?
Second question concerns the kernel driver, and to be frank my inability
to keep up with the fedora build process. I get:
> make: *** /lib/modules/2.6.11-1.14_FC3/source: No such file or
> directory. Stop.
Turns out no modules source directory was installed with this kernel
rpm, though it does exist for older kernels. Any tips? I'm guessing this
is an issue with the kernel rpm?
Any help appreciated.
Mark
[-- Attachment #2: mark.vcf --]
[-- Type: text/x-vcard, Size: 418 bytes --]
begin:vcard
fn:Mark Watson
n:Watson;Mark
org:Volantis Systems
adr:Occam Road;;1 Chancellor Court;Guildford;Surrey;GU9 7YT;UK
email;internet:mark@volantis.com
title:Co-Founder and Chief Technology Officer
tel;work:+44 1483 739777
tel;fax:+44 1483 739739
tel;cell:+44 771 489 9417
note:Assistant = Zoe Jones, +44 1483 739773, zoe.jones@volantis.com
x-mozilla-html:TRUE
url:http://www.volantis.com
version:2.1
end:vcard
next reply other threads:[~2005-05-15 0:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-15 0:47 Mark Watson [this message]
2005-05-15 1:08 ` [Bluez-devel] Building btsco for Fedora 3 Henryk Plötz
2005-05-15 6:02 ` Brad Midgley
2005-05-15 15:04 ` Mark Watson
2005-05-15 19:14 ` Brad Midgley
2005-05-15 19:58 ` Mark Watson
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=42869C29.3040001@volantis.com \
--to=mark@volantis.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 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.