Ok, now I feel a bit of a fool, this does seem to be a bug either in the kernel source (non-debian), or in the way kernel-package parses v2.4 info.
I looked at my last mail and realized I was builing a "test" kernel on an "unstable" system. I logged into my workstation running "stable" with 2.2.17 kernel & sources, and make-kpkg worked just as it should. This is very similar to my first kernel build, for months I kept getting weird compile errors that I couldn't understand, being very new to linux at the time. One day it worked, and has since, never did figure out what I was doing wrong. To clarify some questions asked: On Sun, Jan 21, 2001 at 07:03:14PM +0100, Diego Biurrun wrote: :On Sun, Jan 21, 2001 at 12:08:43PM -0500, Jonathan D. Proulx wrote: :The difference is very subtle, but what I always do is : :sudo make-kpkg --revision custom.1.0 kernel_image : ^^ ^ Doesn't make a difference. :I am not sure this makes a big difference but try it out. You don't need :the "arch" flag if you are compiling on i386 for i386. Shouldn't but for some reason this variable was defaulting to "i386-none" which is invalid (there's no linux/arch/i386-none directory) : :> Why is CROSS_COMPILE defined? The .config builds fine with generic : :I assume because you set arch to any value. Yes, that's exactly it. Thanks, -Jon
