I've been trying to do an emerge -u world for about two weeks now. Every time it get's to alsa-driver-1.0.8_rc1, it crashes. Here's the error message I'm getting. Any ideas?
Thanks! Mike
gcc -D__KERNEL__ -DMODULE=1 -I/var/tmp/portage/alsa-driver-1.0.8_rc1/work/alsa-driver-1.0.8rc1/include -I/usr/src/linux/include -I/usr/src/linux/include -O2 -DLINUX -Wall -Wstrict-prototypes -fomit-frame-pointer -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -DALSA_BUILD -nostdinc -iwithprefix include -DKBUILD_BASENAME=pcxhr_hwdep -c -o pcxhr_hwdep.o pcxhr_hwdep.c
pcxhr_hwdep.c: In function `pcxhr_setup_firmware':
pcxhr_hwdep.c:212: error: structure has no member named `dev'
make[2]: *** [pcxhr_hwdep.o] Error 1
make[2]: Leaving directory `/var/tmp/portage/alsa-driver-1.0.8_rc1/work/alsa-driver-1.0.8rc1/pci/pcxhr'
make[1]: *** [_modsubdir_pcxhr] Error 2
make[1]: Leaving directory `/var/tmp/portage/alsa-driver-1.0.8_rc1/work/alsa-driver-1.0.8rc1/pci'
make: *** [compile] Error 1
!!! ERROR: media-sound/alsa-driver-1.0.8_rc1 failed.
!!! Function src_compile, Line 76, Exitcode 2
!!! Parallel Make Failed
!!! If you need support, post the topmost build error, NOT this status message.
-- gentoo-user@gentoo.org mailing list
Well first of all, if you've been prevented from doing an emerge -u world for *two weeks*, the very first thing you want is to get that finished and then worry about what's wrong with alsa-driver.
So do the emerge -u world yet again, and when alsa-driver crashes, do an
emerge --resume --skip-first
and get the rest of the update done. If anything else crashes because alsa-driver did not install, just skip that too, the same way. Don't do any other emerges in between, or Portage will lose its "list" and you will have to start over with updating and skipping (although the list should be shorter, since some things would have emerged).
Now as to what's going wrong with alsa driver... I often find that if I do not physically have the device, that some modules for specifically multimedia devices will not compile.
I don't know what device this module is for, but do you? Do you actually have it? If not, then just remove it from the config-- or rather, add the "ALSA_CARDS=your_card's_alsa_name" setting to /etc/make.conf to only build drivers for the card you actually have, rather than all of them, and see if it will build then.
What kernel are you using, anyway? Do you even need alsa-driver? There's really no benefit to having to deal with this (fairly annoying) package if you're using a 2.6-series kernel, which has the ALSA drivers already included.
HTH, Holly
-- gentoo-user@gentoo.org mailing list
