Problem compiling 1.0.7 and 1.0.8rc1 on Linux 2.6.9mm1

Problem compiling 1.0.7 and 1.0.8rc1 on Linux 2.6.9mm1

[Yon Mercury]

Hi there,

I'm looking for a bit of help compiling alsa from source on my laptop-
kernel is 2.6.9mm1 (w/ preempt patch)--
alsa is 1.0.7 and 1.0.8rc1- both report the same error

I tried with GCC versions 3.2 and 3.3-- to no avail! Here's the error message:

make -C /lib/modules/2.6.9/source SUBDIRS=/usr/src/alsa-driver-1.0.8rc1
O=/lib/modules/2.6.9/build modules
make[1]: Entering directory `/usr/src/linux-2.6.9'
  CC [M]  /usr/src/alsa-driver-1.0.8rc1/acore/memalloc.o
/usr/src/alsa-driver-1.0.8rc1/acore/memalloc.c:53: error: initializer element
is not constant
/usr/src/alsa-driver-1.0.8rc1/acore/memalloc.c:53: error: (near initialization
for `__param_arr_enable.num')
make[4]: *** [/usr/src/alsa-driver-1.0.8rc1/acore/memalloc.o] Error 1
make[3]: *** [/usr/src/alsa-driver-1.0.8rc1/acore] Error 2
make[2]: *** [_module_/usr/src/alsa-driver-1.0.8rc1] Error 2
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.9'
make: *** [compile] Error 2

Do any of you have an idea where this is coming from?

Thanks,
JP Mercury


-------------------------------------------------------
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/

Re: Problem compiling 1.0.7 and 1.0.8rc1 on Linux 2.6.9mm1

[Takashi Iwai]

At Sat, 25 Dec 2004 17:09:35 -0700,
Yon Mercury wrote:
> 
> Hi there,
> 
> I'm looking for a bit of help compiling alsa from source on my laptop-
> kernel is 2.6.9mm1 (w/ preempt patch)--
> alsa is 1.0.7 and 1.0.8rc1- both report the same error
> 
> I tried with GCC versions 3.2 and 3.3-- to no avail! Here's the error message:

Perhaps 2.6.9-mm1 already includes Rusty's changes for
module_param_array().  alsa-driver checks its from the kernel version
number, so the workaround for the old version is activated even though
mm kernel has the new one.

Try to modify adriver.h:559 from (2,6,10) to (2,6,9).
Or, try 2.6.10 instead :)


Takashi


-------------------------------------------------------
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/