While trying to emerge a number of seperate packages (see reference URL for my particular list), Portage would spit out errors at me like this: checking for built-in ALSA ... "yes" configure: error: You have built-in ALSA in your kernel. And then it would halt. I tracked the problem package to be media-sound/alsa-driver-1.0.5a which is required by a number of ebuilds, but apparently doesn't play nice with a built-in ALSA system in my kernel. Reproducible: Always Steps to Reproduce: SETUP: Have a 2.6 kernel with ALSA already built-in 1. emerge media-sound/alsa-driver-1.0.5a or a package that depends on it. 2. Wait for Portage to spaz 3. Enjoy. Actual Results: Nothing serious, it just halts after finding out that ALSA is built-in. However, since other packages may depend on media-sound/alsa-driver-1.0.5a, it can do a nice job of delaying your emerge. Expected Results: Any package that requires media-sound/alsa-driver-1.0.5a should itself check (as media-sound/alsa-driver-1.0.5a does) to see if ALSA is already built-in, and only require the package if it doesn't already exist. Or, alternately, the media-sound/alsa-driver-1.0.5a package could insert a stub of itself if it already detects ALSA in the kernel, so that it would act intelligently instead of just crashing. Either way, it should do the Right Thing when it relizes what you have in your kernel. I bypassed this bug by doing "emerge -i media-sound/alsa-driver-1.0.5a" which inserts a stub.
youu don't have include/linux/modversions.h which is because you didn't compile that kernel yet.
