From: Jerry Geis <jgeis@messagenetsystems.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] btsco.41 not compiling
Date: Fri, 13 Jan 2006 11:43:36 -0500 [thread overview]
Message-ID: <43C7D8B8.1060701@messagenetsystems.com> (raw)
In-Reply-To: <43C7D767.8080501@xmission.com>
[-- Attachment #1: Type: text/plain, Size: 2837 bytes --]
gcc -version reports 3.4.4
I am running a redhat kernel uname -r gives 2.6.9.-22.0.1-EL
My machine compiles alsa-drivers just fine. It has all kinds of
module_param_array statesments also....
Why would this be failing?
Jerry Geis
MessageNet Systems
101 East Carmel Dr. Suite 105
Carmel, IN 46032
(317)566-1677
(317)663-0808 Fax
Brad Midgley wrote:
>Jerry
>
>what compiler are you using again?
>
>also something may have changed from your 2.6.9 to 2.6.15. we've only
>been tracking the current kernel.
>
>brad
>
>
>
>>I downloaded btsc.41 today. did the ./bootsrap; .configure; make ; make
>>install
>>all that was good.
>>cd kernel; make and I get the following errors from this section of code.
>>
>>
>>static int index[SNDRV_CARDS] = {[0 ... (SNDRV_CARDS - 1)] = -2}; /*
>>Exclude the first card */
>>
>>module_param_array(index, int, NULL, 0444);
>>MODULE_PARM_DESC(index, "Index value for Bluetooth SCO Headset
>>Soundcard.");
>>
>>
>>
>>
>>[root@geisjdell kernel]#
>>[root@geisjdell kernel]# make
>>make[1]: Entering directory `/usr/src/kernels/2.6.9-22.0.1.EL-i686'
>> CC [M] /usr/src/btsco-0.41/kernel/btsco.o
>>/usr/src/btsco-0.41/kernel/btsco.c:88: error: invalid lvalue in unary
>>`&'
>>/usr/src/btsco-0.41/kernel/btsco.c:88: error: initializer element is not
>>constant
>>/usr/src/btsco-0.41/kernel/btsco.c:88: error: (near initialization for
>>`__param_arr_index.num')
>>make[2]: *** [/usr/src/btsco-0.41/kernel/btsco.o] Error 1
>>make[1]: *** [_module_/usr/src/btsco-0.41/kernel] Error 2
>>make[1]: Leaving directory `/usr/src/kernels/2.6.9-22.0.1.EL-i686'
>>make: *** [default] Error 2
>>[root@geisjdell kernel]#
>>
>>-----------------
>>
>>What do I do?
>>
>>I am running centos 4.2, with kernel 2.6.9-22.0.1-EL.
>>alsa 1.0.11rc2
>>
>>Thanks,
>>
>>Jerry
>>
>>
>>
>>
>>
>>-------------------------------------------------------
>>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
>>
>>
>
>
>
>-------------------------------------------------------
>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
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 3887 bytes --]
next prev parent reply other threads:[~2006-01-13 16:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 18:27 [Bluez-users] btsco.41 not compiling Jerry Geis
2006-01-13 16:37 ` Brad Midgley
2006-01-13 16:43 ` Jerry Geis [this message]
2006-01-13 16:47 ` Brad Midgley
2006-01-13 20:14 ` 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=43C7D8B8.1060701@messagenetsystems.com \
--to=jgeis@messagenetsystems.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 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.