>
> Jerry Geis wrote:
> >/ Hi all,
> />/
> />/ I need to compile alsa-project 1.0.16 on the latest centos 5.1 kernel.
> />/ I am getting this error. What to do... ?
> />/
> />/ CC
> />/ [M]
> />/ /home/silentm/MessageNet/alsa-project/alsa-driver-1.0.16/acore/sound_oss.o
> />/ CC
> />/ [M]
> />/ /home/silentm/MessageNet/alsa-project/alsa-driver-1.0.16/acore/info_oss.o
> />/ In file included
> />/ from
> />/ /home/silentm/MessageNet/alsa-project/alsa-driver-1.0.16/acore/../alsa-kernel/core/info_oss.c:29,
> />/
> />/
> />/ from
> />/ /home/silentm/MessageNet/alsa-project/alsa-driver-1.0.16/acore/info_oss.c:7:
> />/
> />/ include/linux/utsname.h:37:52: error: macro "init_utsname" passed 1
> />/ arguments, but takes just 0
> />/ In file included
> />/ from
> />/ /home/silentm/MessageNet/alsa-project/alsa-driver-1.0.16/acore/../alsa-kernel/core/info_oss.c:29,
> />/
> />/
> />/ from
> />/ /home/silentm/MessageNet/alsa-project/alsa-driver-1.0.16/acore/info_oss.c:7:
> />/
> />/ include/linux/utsname.h:38: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> />/ ‘__attribute__’ before ‘{’ token
> />/ make[3]: ***
> />/ [/home/silentm/MessageNet/alsa-project/alsa-driver-1.0.16/acore/info_oss.o]
> />/ Error 1
> />/ make[2]: ***
> />/ [/home/silentm/MessageNet/alsa-project/alsa-driver-1.0.16/acore] Error 2
> />/ make[1]: ***
> />/ [_module_/home/silentm/MessageNet/alsa-project/alsa-driver-1.0.16] Error
> />/ 2
> />/ make[1]: Leaving directory `/usr/src/kernels/2.6.18-53.1.14.el5-x86_64'
> /
> Seems to build OK for me (2.6.18-53.1.14.el5-i386) ...
>
> Did it build OK for previous 5.1 kernels?
>
> Do you know where it is picking include/linux/utsname.h from? - it
> should be:
>
> /lib/modules/2.6.18-53.1.14.el5/build/include/linux/utsname.h
>
> (which is really under /usr/src/kernels/2.6.18-53.1.14.el5-x86_64)
>
> Where does the output of configure say about this?
>
> James Pearson
Jim,
Yes it is getting it from
/lib/modules/2.6.18-53.1.14.el5/build/include/linux/utsname.h
I had to change the driver configure script :
Original:
if test "$kversion.$kpatchlevel" = "2.6" -a $ksublevel -ge 19; then
CONFIG_HAVE_INIT_UTSNAME=1
My version:
if test "$kversion.$kpatchlevel" = "2.6" -a $ksublevel -ge 18; then
CONFIG_HAVE_INIT_UTSNAME=1
Jerry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos/attachments/20080331/6bf35bd2/attachment-0005.html>