I just got done following the GCC migration guide on 3 computers.  It went smoothly on 2 of them, everything works fine, but on the third, after I recompiled the kernel, alsa-driver won't compile.  I'm using vanilla-sources 2.6.14.2, the kernel options are all identical to what they were before I did the GCC migration.  It's getting stuck very early in the ALSA compile:

In file included from /var/tmp/portage/alsa-driver-1.0.10_rc3/work/alsa-driver-1.0.10rc3/include/adriver.h:765,
from /var/tmp/portage/alsa-driver-1.0.10_rc3/work/alsa-driver-1.0.10rc3/acore/sgbuf.c:13:
include/linux/pci.h:392: error: parse error before numeric constant
make[4]: *** [/var/tmp/portage/alsa-driver-1.0.10_rc3/work/alsa-driver-1.0.10rc3/acore/sgbuf.o] Error 1
make[3]: *** [/var/tmp/portage/alsa-driver-1.0.10_rc3/work/alsa-driver-1.0.10rc3/acore] Error 2
make[2]: *** [_module_/var/tmp/portage/alsa-driver-1.0.10_rc3/work/alsa-driver-1.0.10rc3] Error 2
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.14.2'
make: *** [compile] Error 2

!!! ERROR: media-sound/alsa-driver-1.0.10_rc3 failed.
!!! Function src_compile, Line 96, Exitcode 2
!!! Make Failed
!!! If you need support, post the topmost build error, NOT this status message.

I have no idea how to solve this...it's only happening on one computer.  On the others, ALSA compiled fine after recompiling the kernel with the new compiler.  The only change that I made after switching compiler was changing my CFLAGS.  3.3.6 didn't have a --march entry for my processor, so I had to use i686.  After the GCC update, I changed the CFLAGS to --march=c3-2, then I did emerge -e system and emerge -e world afterwards.  Everything but ALSA is working fine.  I'm lost here, I can't imagine what the problem could be.  ALSA would've been recompiled as part of world after the GCC upgrade/CFLAGS change, it must've worked then as I didn't get any errors from the emerge.

Reply via email to