Immediately after compiling kernel 2.6.8-gentoo-r1 (from Livecd minimum 2004.2, stage 1 from internet, complete build from internet) I emerged emu10k1. This resulted in download/compile of 25 packages. The last one ended in an error: !!! ERROR: media-sound/emu10k1-0.20.a-r5 failed. !!! Function pkg_setup, Line 26, Exitcode 1 !!! This module is only compatible with 2.4.x kernels Reproducible: Didn't try Steps to Reproduce: Expected Results: I expected this module not to be included in the emerge in the first place.
I don't see what the bug is. You tried to emerge emu10k1, but it's not compatible with 2.6.x kernels. Perhaps you expected a warning about this before it pulled in all of its dependencies? Please clarify. Thanks.
But of course Patrick; isn't that what all this portage is about? Discovering that a package is not compatible during compile, after downoading and compiling and installing 24 other packages seems a bit besides the point. Or is my understaanding of Portage wrong? Thanks for your attention and your time.
uhm... reassigning to portage team...
localhost jason # emerge -vp media-sound/emu10k1 These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] media-sound/aumix-2.8-r2 -gpm -gtk -gtk2 +nls 0 kB [ebuild N ] media-sound/emu10k1-0.20a-r5 279 kB Most of those 25 packages was probably gtk-related and not actually needed. That's beside the point of the bug, however. Packages are able to specify that they require <=virtual/linux-sources-2.4, but it is entirely up to the user as to what kernel it is actually compiled against. With enhancements in the design, it would be possible for a package to specify to portage requirements on the kernel at /usr/src/linux, but not at the moment. Note, you haven't actually wasted any time if you do move to a 2.4 kernel. If you stay with 2.6, you still haven't really wasted any time if you want anything that depends on gtk, which is very likely.
