During a routine package upgrade ALSA drivers began complaining about the kernel version. after exahusting re-emerges, i tried upgrading the kernel (from 2.4.25_pre7-gss-r8 to -r11). Nothing but errors...mrproper, clean, manual builds, genkernel all result the same. also tried other kernels as well (the gentoo sources) using stock config files. Reproducible: Always Steps to Reproduce: 1. genkernal all --or-- 1. cd /usr/src/linux 2. make clean;make dep;make bzImage Actual Results: make bzImage gcc -D__KERNEL__ -I/usr/src/linux-2.4.26-gentoo-r9/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i586 -DKBUILD_BASENAME=main -c -o init/main.o init/main.c In file included from /usr/src/linux-2.4.26-gentoo-r9/include/linux/unistd.h:9, from init/main.c:17: /usr/src/linux-2.4.26-gentoo-r9/include/asm/unistd.h:375: warning: conflicting types for built-in function '_exit' . scripts/mkversion > .tmpversion gcc -D__KERNEL__ -I/usr/src/linux-2.4.26-gentoo-r9/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i586 -DUTS_MACHINE='"i386"' -DKBUILD_BASENAME=version -c -o init/version.o init/version.c gcc -D__KERNEL__ -I/usr/src/linux-2.4.26-gentoo-r9/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i586 -DKBUILD_BASENAME=do_mounts -c -o init/do_mounts.o init/do_mounts.c In file included from /usr/src/linux-2.4.26-gentoo-r9/include/linux/unistd.h:9, from init/do_mounts.c:5: /usr/src/linux-2.4.26-gentoo-r9/include/asm/unistd.h:375: warning: conflicting types for built-in function '_exit' make CFLAGS="-D__KERNEL__ -I/usr/src/linux-2.4.26-gentoo-r9/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i586 " -C kernel make[1]: Entering directory `/usr/src/linux-2.4.26-gentoo-r9/kernel' make all_targets make[2]: Entering directory `/usr/src/linux-2.4.26-gentoo-r9/kernel' gcc -D__KERNEL__ -I/usr/src/linux-2.4.26-gentoo-r9/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i586 -nostdinc -iwithprefix include -DKBUILD_BASENAME=sched -fno-omit-frame-pointer -c -o sched.o sched.c sched.c:617: error: conflicting types for 'wake_up_process' /usr/src/linux-2.4.26-gentoo-r9/include/linux/sched.h:696: error: previous declaration of 'wake_up_process' was here sched.c:617: error: conflicting types for 'wake_up_process' /usr/src/linux-2.4.26-gentoo-r9/include/linux/sched.h:696: error: previous declaration of 'wake_up_process' was here sched.c:622: error: conflicting types for 'wake_up_forked_process' /usr/src/linux-2.4.26-gentoo-r9/include/linux/sched.h:697: error: previous declaration of 'wake_up_forked_process' was here sched.c:622: error: conflicting types for 'wake_up_forked_process' /usr/src/linux-2.4.26-gentoo-r9/include/linux/sched.h:697: error: previous declaration of 'wake_up_forked_process' was here Expected Results: compiled the kernel tried emerge system with ACCEPT_KEYWORD=~x86 set and then later not set (upgraded, then downgraded). tried unmerging sources and re-emerging them. other packages (even firefox and kde) build fine, and the system runs fine. Main issue is drivers complain "can't find kernel version driver was compiled for". machine is probably not very healthy linux-wise anymore. root@mothra linux # emerge info Portage 2.0.50-r11 (default-x86-1.4, gcc-3.4.2, glibc-2.3.3.20040420-r1, 2.4.25_pre7-gss-r8) ================================================================= System uname: 2.4.25_pre7-gss-r8 i686 AMD Athlon(tm) MP 2000+ Gentoo Base System version 1.4.16 ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=i686 -mtune=athlon-mp -funroll-loops -pipe" CHOST="i486-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/afs/C /etc/afs/afsws /etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=i686 -mtune=athlon-mp -funroll-loops -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://gentoo.osuosl.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X Xaw3d acl acpi afs alsa apache2 apm avi berkdb bitmap-fonts bonobo cdr crypt cscope cups curl dga dvb dvd dvdr encode esd ethereal evo fam fastcgi flash foomaticdb freetds gb gdbm ggi gif gnome gphoto2 gpm gps gstreamer gtk gtk2 gtkhtml guile imap imlib innodb java jikes jpeg kde kerberos krb4 lcms ldap libg++ libgda libwww lirc mad maildir mbox mcal memlimit mikmod mmx motif mozilla mpeg mpi mysql nas ncurses nls odbc oggvorbis opengl pam pcmcia pda pdflib perl plotutils png pnp postgres ppds python qt quicktime readline samba sasl scanner sdl slang slp snmp socks5 spell sse ssl svga tcltk tcpd tetex tiff truetype trusted usb wmf wxwindows x86 xface xinerama xml xml2 xmms xosd xprint xv zeo zlib"
gss-sources is pretty broken, I wouldn't bother with that, gentoo-sources compilation problems are probably gcc 3.4 related. Can you please try with gcc 3.3? Also, I think vanilla-sources-2.4.27 should compile fine with gcc 3.4.
Please reopen with requested info.
Thanks. Actually, revdep-rebuild fixed things, a few files were broken. the man page for revdep-rebuild was especially useful. don't know why i hadn't found it before. should be more publicized. great tool. ended up going for 2.6.8 anyway, gcc 3.4 seems to be just what the doctor ordered if you're after a whacked system. gcc 3.3 works when gcc 3.4 fails, probably shouldn't mix the two, but too late for that now :|
Ok, so do any issues remain in this bug?
besides not compiling with gcc 3.4, which seems to be understood... guess we can close this one, but i would say the resolution was 1. revdep-rebuild 2. gcc 3.3
