Julien Patrick Claassen <[EMAIL PROTECTED]> wrote: > I don't know much about alsa-compilation, but this sounds more like a gcc > problem. Which version are you using? Iheard, that there are lots of problems > between gcc 2.9.x and gcc 3.x. If you have an older gcc version, maybe you'd > try updating it.
That was in reference to a non-quoted earlier post by T.P. Reitzel <[EMAIL PROTECTED]>: > I get the following error trying to compile .9rc8's alsa-driver package > on Slackware 8.1 (2.4.18 kernel): > > make[1]: Entering directory `/usr/src/alsa/alsa-driver-0.9.0rc8/acore' > gcc -D__KERNEL__ -DMODULE=1 -I/usr/src/alsa/alsa-driver-0.9.0rc8/include > -I/lib/modules/2.4.18/build/include -O2 -mpreferred-stack-boundary=2 > -march=i686 -DLINUX -Wall -Wstrict-prototypes -fomit-frame-pointer > -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -DALSA_BUILD > -DEXPORT_SYMTAB -c memalloc.c > memalloc.c:33: `snd_compat_vmalloc_to_page' undeclared here (not in a > function) > memalloc.c:33: initializer element is not constant > memalloc.c:33: (near initialization for > `__ksymtab_snd_compat_vmalloc_to_page.value') > make[1]: *** [memalloc.o] Error 1 > make[1]: Leaving directory `/usr/src/alsa/alsa-driver-0.9.0rc8/acore' > make: *** [compile] Error 1 FWIW, I'm running rh 8.0 with gcc-3.2-7 and kernel-2.4.18-19.8.0 [athlon], and I get a similar error -- here's the tail of the error message: |> memalloc.c:33: `snd_compat_vmalloc_to_page' undeclared here (not in a function) |> memalloc.c:33: initializer element is not constant |> memalloc.c:33: (near initialization for `__ksymtab_snd_compat_vmalloc_to_page.value') |> make[1]: *** [memalloc.o] Error 1 |> make[1]: Leaving directory `/u3/usr/src/redhat/BUILD/alsa-driver-0.9.0rc8/acore' |> make: *** [compile] Error 1 |> error: Bad exit status from /var/tmp/rpm-tmp.66500 (%build) So it doesn't look like a gcc-2.9.x problem from here (unless the alsa developers are using 2.9.x ???) Also during the build of this release and the .9rc7's I got a huge number of warnings like the following: |> In file included from /u3/usr/src/redhat/BUILD/alsa-driver-0.9.0rc8/include/sound/driver.h:43, |> from vxpocket.c:33, |> from vxp440.c:14: |> /u3/usr/src/redhat/BUILD/alsa-driver-0.9.0rc8/include/adriver.h:325:1: warning: "vmalloc_to_page" redefined |> In file included from /usr/src/linux-2.4.18-19.8.0/include/linux/modversions.h:1373, |> from /u3/usr/src/redhat/BUILD/alsa-driver-0.9.0rc8/include/adriver.h:40, |> from /u3/usr/src/redhat/BUILD/alsa-driver-0.9.0rc8/include/sound/driver.h:43, |> from vxpocket.c:33, |> from vxp440.c:14: |> /usr/src/linux-2.4.18-19.8.0/include/linux/modules/ksyms.ver:3649:1: warning: this is the location of the previous definition These did not occur in the rc6's at all. This is caused by the following: |> % grep -n vmalloc_to_page /usr/src/linux-2.4.18-19.8.0/include/linux/modules/ksyms.ver |> 3649 #define vmalloc_to_page _set_ver(vmalloc_to_page) And from the alsa-driver package: |> /usr/src/redhat/BUILD/alsa-driver-0.9.0rc8/include/adriver.h |> 322 /* vmalloc_to_page wrapper */ |> 323 #if LINUX_VERSION_CODE < KERNEL_VERSION(2, 4, 19) |> 324 struct page *snd_compat_vmalloc_to_page(void *addr); |> 325 #define vmalloc_to_page(addr) snd_compat_vmalloc_to_page(addr) |> 326 #endif Won't try to say this one is as serious, but the 9rc7's sound a lot worse and gave many more problems on both my boxen than the 9rc6's did (and I switched back to them for that reason). However, I suspect that the alsa-driver-0.9.0rc8 has a serious compile bug -- for my system and some others, at least. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
