...and at the same time it does. The problem here lies in in a kernel config symbol. CONFIG_SOUND_OSS_CORE can't be defined separately and also without defining CONFIG_SND. The second would break the ebuild and to get the first, you'd need to mark one of the oss compatibility options in menuconfig - that would probably conflict with those from alsa-driver. To get around it, I added a small patch to alsa-driver, defining CONFIG_SOUND_OSS_CORE in configure.in (probably not really needed) and patched kernel sources: added 'select SOUND_OSS_CORE' in 'menuconfig SOUND' block of sound/Kconfig. Well, it works for me.
A bump to alsa-driver-1.0.19 does not seem to fix this. Not been able to find the cause (yet).
One simple but ugly way to work around this is just to select OSS at the top level and select nothing underneath it. This selects CONFIG_SOUND_PRIME which selects CONFIG_SOUND_OSS_CORE and nothing else. This could if conditional on USE=oss in the alsa-driver ebuild. This can probably be our last resort.
I think this is probably same as bug 320583
Well, no. Since I filed this bug, I learned the reason why the things are done that way - it's to make things like osspd work. This obviously doesn't help with the proble here.
Still valid with 1.0.23?
dropped
