Summary: | Alsa build error | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Chris Moore <kurisu> |
Component: | New packages | Assignee: | Arcady Genkin (RETIRED) <agenkin> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | richardj |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Chris Moore
2002-07-11 11:39:25 UTC
what kernel are you using? I was having the same problem with alsa-driver builds. So I decided to build by hand and every thing built fine. So went looking for the diferance. When doing this by hand Alsa looks for the kernel headers in /lib/modules/"what ever kernel is running"/build/include where build is a symlink to the sources for the kernel. The ebuild on the other and passes a option to configure to force the kernel include path to be /usr/src/linux. Well there is a problem here if you have updated your kernel but not the symlink. So To fix this change the symlink /usr/src/linux to point to the actual kernel you are running. Once that is done every thing works as expected. I really think the ebuild should not force the kernel include path but let configure figure it out. That way if I update my kernel it will get the right include files. On the other hand maybe the ebuild for the kernel souces should be changed to fix the symlink but that may not be right either as I may just insall the sources but not actualy build and install that particular kernel. Chris, are you still there? I'm closing this bug for the lack of feedback from you. If you are still experiencing the problem, then make sure that /usr/linux points to the correct kernel sourses and re-open the bug. Richard, I dissagree with you; I think that relying too hard on the configure script causes too many headaches. Especially ones line unreproducible bugs. |