HELP!! 2.6.x build problem with make xconfig

Please don't flame me for missing this if it's already buried in the archive but I cannot make xconfig, gconfig, or menuconfig with a 2.6.X kernel.

I am using RH 9.0 with all up2dates (including required packages for 2.6.x kernel build as far as I can tell). Am I missing a symbolic link or something?

Here's what I do (as root)...

cd /usr/src
rm linux linux-2.4 linux-2.6
tar -zxvf linux-2.6.x.tar.gz
chown -R 0.0 linux-2.6.x
ln -fs linux-2.6.x linux
ln -fs linux-2.4.x linux-2.6 # not sure why I do this anymore
cd /usr/include
rm asm linux scsi
ln -fs /usr/src/linux/include/asm-i386 asm
ln -fs /usr/src/linux/include/linux linux
ln -fs /usr/src/linux/include/scsi scsi
cd /usr/src/linux-2.6.x
make mrproper xconfig

<!-- My error follows -->

In file included from /usr/include/linux/errno.h:4,

                 from /usr/include/bits/errno.h:25,
                 from /usr/include/errno.h:36,
                 from scripts/kconfig/mconf.c:12:

/usr/include/asm/errno.h:4:31: asm-generic/errno.h: No such file or directory
scripts/kconfig/mconf.c: In function `exec_conf':
scripts/kconfig/mconf.c:243: `EINTR' undeclared (first use in this function)
scripts/kconfig/mconf.c:243: (Each undeclared identifier is reported only once
scripts/kconfig/mconf.c:243: for each function it appears in.) scripts/kconfig/mconf.c:243: `EAGAIN' undeclared (first use in this function)
make[1]: *** [scripts/kconfig/mconf.o] Error 1
make: *** [xconfig] Error 2

<!-- If I do a make gconfig, I get the following -->

In file included from /usr/include/gtk-2.0/gtk/gtk.h:90,
from scripts/kconfig/gconf.c:17:
/usr/include/gtk-2.0/gtk/gtkitemfactory.h:51: warning: function declaration isn't a prototype
scripts/kconfig/images.c:6: warning: xpm_load' defined but not used scripts/kconfig/images.c:36: warning: xpm_save' defined but not used scripts/kconfig/images.c:66: warning: xpm_back' defined but not used scripts/kconfig/images.c:175: warning: xpm_symbol_no' defined but not used
scripts/kconfig/images.c:192: warning: `xpm_symbol_mod' defined but not used
scripts/kconfig/images.c:209: warning: `xpm_symbol_yes' defined but not used
scripts/kconfig/images.c:226: warning: `xpm_choice_no' defined but not used
scripts/kconfig/images.c:243: warning: `xpm_choice_yes' defined but not used
scripts/kconfig/images.c:277: warning: `xpm_menu_inv' defined but not used
scripts/kconfig/images.c:294: warning: `xpm_menuback' defined but not used
scripts/kconfig/gconf.c:981: warning: `renderer_toggled' defined but not used
In file included from /usr/include/linux/errno.h:4,

                 from /usr/include/bits/errno.h:25,
                 from /usr/include/errno.h:36,
                 from scripts/kconfig/mconf.c:12:

/usr/include/asm/errno.h:4:31: asm-generic/errno.h: No such file or directory
scripts/kconfig/mconf.c: In function `exec_conf':
scripts/kconfig/mconf.c:243: `EINTR' undeclared (first use in this function)
scripts/kconfig/mconf.c:243: (Each undeclared identifier is reported only once
scripts/kconfig/mconf.c:243: for each function it appears in.) scripts/kconfig/mconf.c:243: `EAGAIN' undeclared (first use in this function)
make[1]: *** [scripts/kconfig/mconf.o] Error 1
make: *** [gconfig] Error 2

Please help or point me to a FAW or something...

Thanks

JOB

Don't do that.

Use what's in the glibc-kernheaders RPM for userspace, and let the kernel provide its own headers for its use.

GNU libc doesn't have (nor need) its own "kernel" headers and uses the kernel ones.
You may live with "glibc-kernheaders" package only if it matches your system. If you're using a different (newer, modified etc) kernel then you need the symlinks or a copy (example: new ioctls + programs using them).

You may need to recompile the libc as well, if the libc-kernel (binary) interface has changed.

Krzysztof Halasa, B*FH

Sometimes there's a reason to use the old kernel headers...I still run several apps that can't grok the 2.6 headers, and will only compile with 2.4 ones (and they work fine). I have a couple of small scripts that switch the directories around when I need them, for convenience. :)

Of course, the real solution would be to hack them to work with new headers, but I don't have the time for that at the moment. *Sigh*

Javier Fernandez-Ivern