CC kernel/power/poweroff.o In file included from kernel/power/poweroff.c:8: include/linux/sysrq.h: In function `__reterr': include/linux/sysrq.h:42: error: `EINVAL' undeclared (first use in this function) include/linux/sysrq.h:42: error: (Each undeclared identifier is reported only once include/linux/sysrq.h:42: error: for each function it appears in.) kernel/power/poweroff.c: At top level: kernel/power/poweroff.c:32: warning: `sysrq_poweroff_op' defined but not used make[2]: *** [kernel/power/poweroff.o] Error 1 make[1]: *** [kernel/power] Error 2 make: *** [kernel] Error 2 Reproducible: Always Steps to Reproduce: After installing gentoo-dev-sources-2.6.10-r4, and updating .config, just type "make" :) Actual Results: See above Expected Results: A nice, new 2.6.10 kernel. :) Portage 2.0.51-r3 (default-linux/x86/2004.2, gcc-3.3.4, glibc-2.3.4.20040808-r1, 2.6. 9-gentoo-r12 i686) ================================================================= System uname: 2.6.9-gentoo-r12 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.90.0.1.1-r3 Headers: sys-kernel/linux26-headers-2.6.8.1-r2 Libtools: sys-devel/libtool-1.5.2-r7 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=pentium4 -O3 -pipe -fomit-frame-pointer -msse2 -mfpmath=sse" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/share/ config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mcpu=i686 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="http://gentoo.osuosl.org http://distro.ibiblio.org/pub/Linux/ distributions/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X aalib acpi alsa apache2 arts avi berkdb bitmap-fonts caps cdparanoia cdr crypt cups dga directfb divx4linux dvd dvdr encode faad fam fbcon flac gd ggi gif gmp gphoto2 gpm gtk2 idea imagemagick imap imlib ipv6 javascript jikes joystick jpeg kde lcms libwww live mad matroska mbox memlimit mmx mmx2 mpeg mpi mysql nas ncurses network nls nomotif nptl oggvorbis opengl pam pdflib perl png qt quicktime readline rtc samba scanner sdl silc speex spell sse sse2 ssl svga tcpd theora tiff truetype unicode usb vanilla wifi wmf xinerama xml2 xmms xv xvid zlib linguas_en linguas_ru"
Please attach your .config
Created attachment 48225 [details] As titled (I hope :) ), my .config file I don't the "proper" way to attach a .config (never done it before), so I used bzip2 to compress it.
Please just attach it as text/plain so that it is readable and easy to access.
Created attachment 48233 [details] .config file (in text form) Done.
Can't reproduce here. EINVAL is quite an important define, sounds like something has gone missing. Could you try: rm -rf /usr/src/linux-2.6.10-gentoo-r4 emerge gentoo-dev-sources And try again..
OK, I did that (an also recompiled the entire system with gcc 3.3.5). Somewhere, the problem disappeared. :) I had (maybe) a similar problem during the recompile. In one of the packages, one of the files just seemed completely out to lunch. The compile crashed, but the problem disappeared when I tried emerge --resume (without changing anything). I wonder if I have some kind of I/O (SATA) problem. Have to actually boot with 2.6.10 (and that might solve it) to test it further. Thanks.
I think you might be getting confused with something else. "emerging" a kernel does not compile anything, it just unpacks and moves the source files. Thanks for reporting this issue anyway.
> "emerging" a kernel does not compile anything I understand that. I wonder if just unpacking all of those files at once (on an SATA drive - and I have had an issue with my SATA removable drive since 2.6.7, though none with the fixed drive - you might see another bug report soon on that if 2.6.10 does not solve the problem) occasionally spits out a corrupted file. Nothing worse than flaky (difficult to replicate) bugs.