Well.. My lilo boot disk recently crashed (again...) but this time I have real trouble compiling my kernel.
I got a new (full) version of kernel 2.4.17 but I have the same error so my archive isn't corrupted.

Make mrproper --------->No Problem
Make menuconfig------->No Problem
Make dep----------------->No Problem

then, No matter wich command I try I get the same error msg
Make bzImage----------->/usr/include/linux/errno.h:4:asm/errno.h: No Such Files or dirrectory

I get the same error If I do Make Install or Make Modules or Make Modules_Install or anything

It,s look like to be an error with a symlink or something
I tried to change the installation directory (so /usr/src/linux-2.4.7 to /usr/src/linux to /usr/src/test ) nothing work

It's not the first time I compile my kernel but the last time was some time ago and I was with someone better than me...

any idea someone?

well asm/errno.h comes from the kernel-headers rpm if you're using an rpm kernel. so if you install the hedares for you default kernel it should work. however the files should also be in /usr/src/linux-x.y.z/include/asm-i386 so there may be a way to define the use of that point instead of the default rpm ones.

stop press. learning curve alert.

ok, so the asm headers are defined by a link in /usr/src/linux-x.y.z/include/ FROM asm-*your arch name here* to just asm, check that link is there, if not, make it, and you might be ok. seems like a very strange problem. I'd presume that link is made within the menuconfig section... hmmm

I'm not using rpm i'm on slakware so it can't work anyway. Hum I will try to make the link but hum.. I recently change the size of my linux partition (and It make lilo to crash...) but can it cause trouble about symlink?
Dunno maybe symlink need disk sector? hum?

I had this problem recently after recompiling up to 2.4.16. The symlink isn't there by default so you need to make it. errno.h is looking at the asm@ symlink in /usr/include that points to /usr/src/linux/asm so that's ok if you are using linux as the compile dir. If not, edit that one and change the linux to linux-2.4.x then as said above, go to /usr/src/linux/include and you'll see asm directories up the wazoo. Just type: ln -s asm-i386 asm
Then you should be all set with no more errno's about asm anyhow.

I had this problem recently after recompiling up to 2.4.16. The symlink isn't there by default so you need to make it. errno.h is looking at the asm@ symlink in /usr/include that points to /usr/src/linux/asm so that's ok if you are using linux as the compile dir. If not, edit that one and change the linux to linux-2.4.x then as said above, go to /usr/src/linux/include and you'll see asm directories up the wazoo. Just type: ln -s asm-i386 asm
Then you should be all set with no more errno's about asm anyhow.

Sorry about the dual-post, i've been having some connection probs lately.

This is what I do in slack,
1.
Add the below entires to your lilo.conf
# Backup Image
image = /vmlinuz.old
root = /dev/hda1
label = oldlinux
Note: replace /dev/hda1 with your boot partition.
2.
make mrproper (I dont do this most of the time since it will remove your .config)
make menuconfig (ncurses based kernel configuration menu system)
make dep (fixor up them dependencies)
make clean (get rid of old o files and stuff)
make bzImage (build it)
make install (read the note below for this one)
make modules (build the modules)
make modules_install (install the modules)
Note: "make install" is one that most don't use but if you run Slackware it will work fine. What it does is: copies, moves, and renames all the files to where they need to be. It also updates lilo for you. This method is very clean fast and easy to use. If your new kernel fails to work you can boot the old one by hitting the left shift key at the lilo prompt during bootup and typing oldlinux.

Soooo that's the next part of my history.

Hum the kernel problem was about symlink,thanx taz.devil, really :0)

But I still having troubles... I can compilate my kernel but my lilo boot isn't working. When I try to "make install" it says something like "/dev/hda7 doesn't contains a primary partition table near line xx il /etc/lilo.conf....
But hum I tried few thing... These error seems to be about my dos partition,so I comment this part... It was not so bad until I restarted my box... Lilo said something like /dev/hda7 look like to not contain linux files partition etc...

Oh? Normal,when I boot my linux (with a bootable cd) I boot it from /dev/hd8. So I edited my lilo.conf again,change my partition... but my stupid lilo still try booting hda7.

Someone tell me to re"start" lilo (so ./lilo) but I'm booting from a lilo disk, so I dont have lilo installed on my hard drive.

But I recently resized my partition? Is this problem can be cause by a oversized linux partition? over hda8 may cause problem with swap so maybe it can cause problem over hd7 with linux ext? hum?
What if I move my partition to a "closer" sector (closer of the zero sector of course) ?

Hum... I'm just scared about moving my partition... Please answer someone