Re: Re: recompile kernel

On Sat, 24 Aug 2002 12:47, Bob Lockie wrote:
> >> >>>I'm getting an error recompiling the kernel.
> >> >>>I did "make dep" successfully.
> >> >>>"make clean bzImage modules modules_install" fails:
> >> >>
> >> >>I originally took out "Symmetric Multiprocessing Support" (the help
> >> >> said I could disable it). It worked when I put it back in.
> >> >
> >> >Unless you don't have an SMP system, you shouldn't have to enable the
> >> >setting.
> >> >Try backing up your .config file, do a "make mrproper", copy the
> >> > .config file back and try again to compile the kernel.
> >>
> >> I can't compile the kernel now.
> >> I must have selected something that requires SMP support?
> >
> >Hey,
> >
> >I would delete your kernel source tree, unpack it again (so you know it is
> >clean) and not prune out so much stuff.  It may or may not have been the
> > SMP support that broke it, but I would examine why you are recompiling
> > the kernel and just satisfy that.
> >
> >If it is merely to upgrade to a later version, then only touch things you
> > need to put in to work with your hardware.  If you are trying new
> > features, then add them in.  Try not too pull too much stuff out until
> > you have your kernel working.  Then later you can experiment a bit more
> > but _do_ expect this to happen.
>
> Ok, I have a working kernel but I'm trying to play with the configuration.
> I thought "make mrproper" would start completely over but I'll get new
> source each time. :-)

Well, mrproper does a thorough job of cleaning, but I don't know that it 
deletes everything it has created.

I think '#make mrproper' will be ok each time, but if it doesn't work, then 
you should start over with new sources.  Maybe a bug in the make system meant 
that make mrproper didn't work? Maybe something else.

FWIW, a friend of mine tried compiling 2.4.19 and did the usual pruning and 
had the make fail as well.  Seems like 2.4.19 isn't as happy to have large 
chunks of code missing as earlier ones.  Which is exactely what you are 
doing. The developers of OpenBSD don't even really like people turning stuff 
off in their kernels, but that is mainly because they really only have the 
resources to test the so called GENERIC kernel (which doesn't have everything 
on, but most things people need everyday).  I don't think the Linux kernel is 
so well endowed with defaults.

Thanks.

Evan.