First, IANAP so I'm guessing here. I haven't been able to emerge any 3.x version of kdelibs on one particular machine. I believe I've finally tracked down the problem. I'm guessing that emerging kdelibs won't run to completion without alsa. The messages I get (for kdelibs-3.1_rc5) are: deviceman.cc:53:33 sound/asound.h: No such file or directory. deviceman.cc:54:37 sound/asequencer.h: No such file or directory. My assumption is that asound.h and asequencer.h are provided by alsa. This is the only machine for which I was not able to get alsa to work. It's a Dell Dimension XPS 400. It's based on a Pentium II 400MHz cpu. The sound chip is included on the motherboard and is a CS 4610. This matches what is reported in /proc/pci (CS 4610/11). However, both under NT and compiled as a linux kernel module only, the driver that works is the OSS CS4232. None of the other available CS drivers in the kernel work and none of the equivalent alsa CS drivers work. (I busted my head for over 2 weeks figuring this out). And the only reason I did was noticing that the working NT sound driver provided by Dell was labelled for CS4232. As best as I can determine, Dell wanted to use the same driver across several different mobos and has tweaked the BIOS on this board to fake the CS4232. The bottom line was that I unmerged alsa and am using the OSS driver. If my guess about asound.h and asequencer.h being provided by alsa is wrong, please let me know. :) And let me know where these files actually come from. Regardless - I can't compile kdelibs because these two c header files are missing. :-)
After emerging alsa-sound, I've confirmed that asound.h and asequencer.h are now in /usr/include/sound. alsa-sound needs to be listed as a dependency for kdelibs. I'm compiling kdelibs now but I won't know the results until tommorrow.
well, if you have no longer alsa installed, it seems the alsa-useflag is still set. please check if 'USE="-alsa" emerge kdelibs' works.
Well, after emerging alsa-sound, I left the computer at work today attempting to emerge kdelibs again. Tomorrow, I'll see if it ran to completion. It didn't occur to me to try setting the USE flag = '-alsa'. I did, however look in make.conf, make.gobals and make.defaults and did not see 'alsa' anywhere. I guess, after checking to see if kdelib completes, I should unmerge alsa-sound, set the USE flag as you indicated and try to emerge kdelib again. Is this correct?
yup, that's what i'm suggesting.
OK - this is the scoop. :-) the 'emerge kdelibs' I started last night completed successfully (this is the one after emerging alsa' As confirmation: I grepped make.conf and make.globals for alsa and found nothing. I grepped directory make.profile for alsa. Alsa was not in make.defaults but was in virtuals. Does this mean that the kdelib ebuild itself has alsa set by default? I updated make.conf with USE="-alsa". I unmerged alsa and I'm re-emerging kdelibs again. On this machine - that's an all day process so I don't know if I'll be able to report success today but I do expect to do so on Monday. Thanx for the help!
Mon: emerge ran through to completion. I have no problem with this issue being closed. Best regards. Guy
kdelibs currently depends on alsa? ( media-libs/alsa-lib ). since i'm not using alsa, please report which package provides asound.h and asequencer.h, cause kdelibs should depend on this package (you speak about alsa-sound, which i can't find here). USE=alsa is set if alsa-lib is merged (according to profiles/default-x86-1.4/use.defaults). thanks.
just found the same bug with answers to my questions: bug 11996 since that is the older one, i will mark this as duplicate. *** This bug has been marked as a duplicate of 11996 ***
