From: usenet@solar-empire.de   
      
   Christian Pontesegger  wrote:   
   > Marc Christiansen wrote:   
   >> My make.conf does not contain this line and ALSA works. The only alsa   
   >> line I have, is ALSA_CARDS="ens1371 virmidi".   
   >   
   > I do not have that line. Regarding the alsa howto its related to the   
   > alsa-driver package.   
   >   
   > I compiled alsa directly into the kernel and did compile everything   
   > directly and not as modul.e   
      
   Maybe some leftover on my system. I'm using the kernel driver too, but   
   as modules.   
      
   >> What version of sys-apps/portage do you have? I'm using portage-2.1.3.19   
   >> and I get different output:   
   >   
   > I have the same portage version.   
      
   Well, was worth a try.   
      
   >> Mayby your prtage is to old? Just a guess. Does the output of "emerge   
   >> --info --verbose | grep USE_EXPAND" show ALSA_CARDS and   
   >> ALSA_PCM_PLUGINS?   
   >   
   > No, I get:   
   >   
   > USE_EXPAND="CROSSCOMPILE_OPTS DVB_CARDS ELIBC FCDSL_CARDS   
   > FOO2ZJS_DEVICES FRITZCAPI_CARDS INPUT_DEVICES KERNEL LINGUAS   
   > LIRC_DEVICES MISDN_CARDS USERLAND VIDEO_CARDS"   
   >   
   >> And "emerge --info | grep ALSA" should show them too,   
   >> in the line with the use flags.   
   >   
   > I do not get any output for that command.   
   >   
   >   
   > So it seems its portage, so here is my "emerge --info", maybe this helps:   
   >   
   > Portage 2.1.3.19 (!../usr/portage/profiles/default-linux/x86/2006.1,   
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   
   This looks suspicious. If I change /etc/make.profile to the 2006.1   
   profile (I'm using 2007.0/desktop), the output of emerge --info starts with:   
    Portage 2.1.3.19 (default-linux/x86/2006.1, gcc-4.1.2, glibc-2.6.1-r0,   
      
   but still contains ALSA_PCM_PLUGINS and ALSA_CARDS.   
      
   Together with   
   [...]   
   > DISTDIR="/mnt/portage/distfiles"   
   [...]   
   > PKGDIR="/mnt/portage/packages"   
   [...]   
   > PORTDIR="/mnt/portage"   
      
   and the fact, that your USE_EXPAND does not contain the alsa vars makes   
   me think your /etc/make.profile points to the wrong target. If I'm not   
   mistaken, on your system either /usr/portage should be a link to   
   /mnt/portage or /etc/make.profile should be a link to   
   '/mnt/portage/profiles/default-linux/x86/2006.1'.   
      
   This is my /etc/make.profile:   
   0:jupiter etc # ls -l /etc/make.profile   
   lrwxrwxrwx 1 root root 56 2007-11-19 12:30 /etc/make.profile ->   
   ../usr/portage/profiles/default-linux/x86/2007.0/desktop   
      
   I have PORTDIR="/usr/portage".   
      
   So, you could try somethink like this:   
   # save the old link   
   mv /etc/make.profile /etc/make.profile-save   
   # and create the (hopefully) correct one   
   ln -s /mnt/portage/profiles/default-linux/x86/2006.1 /etc/make.profile   
      
   Then check emerge --info for the ALSA vars.   
      
   If this works, you might want to rename /usr/portage to e.g.   
   /usr/portage-old and either see what breaks, because it uses   
   /usr/portage instead of $PORTDIR or create a link:   
   ln -s /mnt/portage /usr/portage   
      
   Marc   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)