Summary: | alsa-driver 1.0.13 fails to compile with linux kernel 2.6.19-rc1 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sylvain BERTRAND <sylvain.bertrand> |
Component: | [OLD] Core system | Assignee: | Gentoo ALSA team [DISABLED] <alsa-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | fen1x |
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | patch to make alsa-headers-9999 and alsa-driver-9999 work |
Description
Sylvain BERTRAND
2006-10-11 07:37:43 UTC
Kindly review https://bugs.gentoo.org/page.cgi?id=fields.html#bug_severity; also post some errors, we are missing paranormal skills. make -C /usr/src/linux M=/var/tmp/portage/alsa-driver-1.0.13/work/alsa-driver-1.0.13 O=/usr/src/linux CPP="i686-pc-linux-gnu-gcc -E" CC="i686-pc-linux-gnu-gcc" modules make[1]: Entering directory `/usr/src/linux-2.6.19-rc1' CC [M] /var/tmp/portage/alsa-driver-1.0.13/work/alsa-driver-1.0.13/acore/hwdep.o CC [M] /var/tmp/portage/alsa-driver-1.0.13/work/alsa-driver-1.0.13/acore/memalloc.o In file included from /var/tmp/portage/alsa-driver-1.0.13/work/alsa-driver-1.0.13/acore/memalloc.inc:1, from /var/tmp/portage/alsa-driver-1.0.13/work/alsa-driver-1.0.13/acore/memalloc.c:1: include/linux/config.h:6:2: warning: #warning Including config.h is deprecated. In file included from /var/tmp/portage/alsa-driver-1.0.13/work/alsa-driver-1.0.13/acore/memalloc.inc:1, from /var/tmp/portage/alsa-driver-1.0.13/work/alsa-driver-1.0.13/acore/memalloc.c:1: include/linux/config.h:6:2: warning: #warning Including config.h is deprecated. CC [M] /var/tmp/portage/alsa-driver-1.0.13/work/alsa-driver-1.0.13/acore/sgbuf.o In file included from /var/tmp/portage/alsa-driver-1.0.13/work/alsa-driver-1.0.13/acore/sgbuf.c:2: include/linux/config.h:6:2: warning: #warning Including config.h is deprecated. CC [M] /var/tmp/portage/alsa-driver-1.0.13/work/alsa-driver-1.0.13/acore/memory_wrapper.o In file included from /var/tmp/portage/alsa-driver-1.0.13/work/alsa-driver-1.0.13/acore/memory_wrapper.c:2: include/linux/config.h:6:2: warning: #warning Including config.h is deprecated. CC [M] /var/tmp/portage/alsa-driver-1.0.13/work/alsa-driver-1.0.13/acore/pcm.o CC [M] /var/tmp/portage/alsa-driver-1.0.13/work/alsa-driver-1.0.13/acore/pcm_native.o /var/tmp/portage/alsa-driver-1.0.13/work/alsa-driver-1.0.13/acore/pcm_native.c:3569: error: unknown field 'writev' specified in initializer /var/tmp/portage/alsa-driver-1.0.13/work/alsa-driver-1.0.13/acore/pcm_native.c:3569: warning: initialization from incompatible pointer type /var/tmp/portage/alsa-driver-1.0.13/work/alsa-driver-1.0.13/acore/pcm_native.c:3589: error: unknown field 'readv' specified in initializer /var/tmp/portage/alsa-driver-1.0.13/work/alsa-driver-1.0.13/acore/pcm_native.c:3589: warning: initialization from incompatible pointer type make[4]: *** [/var/tmp/portage/alsa-driver-1.0.13/work/alsa-driver-1.0.13/acore/pcm_native.o] Error 1 make[3]: *** [/var/tmp/portage/alsa-driver-1.0.13/work/alsa-driver-1.0.13/acore] Error 2 make[2]: *** [_module_/var/tmp/portage/alsa-driver-1.0.13/work/alsa-driver-1.0.13] Error 2 make[1]: *** [modules] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.19-rc1' make: *** [compile] Error 2 Compilation errors go with which severity? Forgot to post the compilation error output... For an RC, normal severity. Anyway *sigh* no release from ALSA upstream just yet, will try to backport from their HG repo. The changes are too extensive to be easily patched, we need to wait for 1.0.14_rc1 to be released. Do we have a alsa-driver-git or something like that? We don't, but I might end up writing an alsa-driver-9999 ebuild with the HG repository, but it's going to take a while, I'm afraid. On the next sync, try with alsa-driver and alsa-headers 9999. Created attachment 99470 [details, diff]
patch to make alsa-headers-9999 and alsa-driver-9999 work
There is still a sandbox violation, don't forget to FEATURES="-sandbox" when emerging. Additionally the conf scripts require to enable firmware loading in the kernel. After all that, at the date of today, with this patch, alsa compiles with 2.6.19-rc1.
This patch is unneeded here, and sandbox works for me, can you show me why it fails? I get this when I try to emerge non-patched alsa-headers-9999: " >>> Emerging (1 of 1) media-sound/alsa-headers-9999 to / * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] >>> Unpacking source... * hg clone http://hg.alsa-project.org/alsa-kernel ... abort: No such file or directory: alsa-driver/alsa-kernel [ !! ] !!! ERROR: media-sound/alsa-headers-9999 failed. Call stack: ebuild.sh, line 1548: Called dyn_unpack ebuild.sh, line 708: Called src_unpack alsa-headers-9999.ebuild, line 29: Called mercurial_fetch 'http://hg.alsa-project.org/alsa-kernel' 'alsa-driver/alsa-kernel' mercurial.eclass, line 54: Called die " ================================================================================ pathed and non-patched alsa-driver give me: >>> Source compiled. --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/var/log/sandbox/sandbox-media-sound_-_alsa-driver-9999-12112.log" open_wr: /usr/src/linux-2.6.19-rc1/astest15152.out open_wr: /usr/src/linux-2.6.19-rc1/astest15156.out open_wr: /usr/src/linux-2.6.19-rc1/astest15163.out open_wr: /usr/src/linux-2.6.19-rc1/astest15167.out -------------------------------------------------------------------------------- I get this sandbox violation anytime I want to emerge something dealing with the kernel. ================================================================================ The patch on alsa-driver-9999 is only usefull to make it "more" in phase (namely sharing the alsa-kernel hg module in the same hg project) with the patched alsa-headers-9999. We should be able to do the same for alsa-lib, alsa-utils and alsa-tools if needed. I _do not_ want this to happen for any other package but -headers and -driver, so I don't really care for big changes here. About that error, I'll try to investigate, works here. Err, there's a separate bug about the fetch issue (Bug 151104) and about the sandbox violation as well (Bug 149307). Suggest closing this one. The patch provided solve the "fetch issue". The idea is to wait for a "gentoo dev official" patch. I move the patch to the "fetch issue" bug #151104 and mark this one as duplicate. *** This bug has been marked as a duplicate of 151104 *** *** Bug 152572 has been marked as a duplicate of this bug. *** |