When I did "make xconfig" after "make oldconfig" a get an error when I try to "Save and exit" saying: can't read "CONFIG_SCSI": no such variable Also the kernel can't be built, compile error: rd.c:88: error: `CONFIG_BLK_DEV_RAM_SIZE' undeclared here (not in a function) This is due to autoconf.h missing most of the defines. Reproducible: Always Steps to Reproduce: 1. emerge -vu world 2. make oldconfig 3. make xconfig or 3. make dep && make bzImage Portage 2.0.49-r7 (default-x86-1.4, gcc-3.3.1, glibc-2.3.2-r1, 2.4.22_pre2-gss) ================================================================= System uname: 2.4.22_pre2-gss i686 Pentium III (Coppermine) ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=pentium3 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /opt/tomcat/conf /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O3 -march=pentium3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="sandbox ccache autoaddcvs" GENTOO_MIRRORS="http://gentoo.oregonstate.edu 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.europe.gentoo.org/gentoo-portage" USE="x86 oss apm arts avi crypt cups encode foomaticdb gif jpeg libg++ mad mikmod mmx mpeg ncurses nls pdflib quicktime sdl spell truetype xmms xv zlib gdbm berkdb slang readline svga java X gpm tcpd pam libwww ssl python esd imlib oggvorbis gnome gtk motif opengl mozilla jikes junit apache2 -kde -qt perl fbcon tcltk xinerama sse xml xml2 -rage12b mach6 png emacs tetex kerberos gcl gtk2"
Created attachment 18798 [details] .config before make oldconfig from 2.4.22_pre2-gss
Created attachment 18799 [details] .config after oldconfig
Created attachment 18800 [details] corrupt autoconf.h
I tried 2.4.23_pre6 from kernel.org and the same problem is there as well...
I think it went away with some later pre release of 2.4.23, I'll report again if it appears again.