I'm building a custom kernel, for the first time on a new 6.2 install. with _everything_ I want/need specified via 'option' and/or 'device' lines in the config file (along with appropriate 'hints' in the hints),

'make buildkernel KERNCONF={mumble}' has been running for *more*than*six*hours* on a Pentium 1 200mhz machine -- and is compiling all sorts of stuff tat I'm _not_using_ in the custom kernel.

I've discovered the 'NO_KERNELCLEAN' flag so it won't start over from scratch -every- time you build a kernel, but this is bloody ridiculous. The _entire_ point of the 'make' facility is to avoid recompiling anything that doesn't _need_ to be re-compiled. Yet the distributed makefile, _by_ _default_ starts off by deleting *EVERY*LAST*OBJECT*FILE*!!!

Is there _any_ way to get the build process to compile -only- what I need?? E.g. to _not_ compile the 'wireless' modules when I've removed all the wireless support from the kernel? or SCSI disk support on an IDE only box or all the Network card drivers that I don't have? or the I2C bus support? or the IPv6 stuff?

My frame-of-reference is compiling BSDi kernels on much smaller hardware. (e.g. a '386' box with a '386-to-486' upgrade processor at 25x2 mhz, with a whopping -eight- megs of RAM. A custom kernel build took around _7_ minutes for a 'router and firewall' box. And produced a monolithic kernel that was well under _one_mb_ in size.)

Are my expectations _that_ far out of line, or is there a real issue here?

Comments -- including those telling me I'm an idiot -- welcomed.