Be careful that you copy the .config to another file before doing
"make mrproper". That wipes out the .config file, and you won't be
able to "make oldconfig" (well, you can, but it will ask you about
EVERYTHING).
I copy the .config to ~/config.2.X.Y.custom (currently 2.2.17), then
copy back to .config after the "make mrproper"
jeff
Rich Payne wrote:
>
> You should be OK, though it may be a little slower. Where did it
> fail? Make sure that it's compiling with kgcc not gcc! RH insisted on
> using gcc-2.96 and that can't compile a kernel, so 2.95 is included as
> kgcc. I've noticed that many times the kernel compile won't go right
> unless you:
>
> make mrproper
> make config (oldconfig)
> make dep boot modules
>
> Take a look at the top level makefile and you'll see what I mean. IMHO,
> this was a silly move on their part. What do you think happens if you
> grab a clean (aka: non-RH) kernel source?
>
> --rdp
>
> On Sun, 1 Oct 2000, Kenneth E. Lussier wrote:
>
> > All,
> >
> > Is there any real danger of compiling SMP support into a kernel if you
> > only have one CPU? It appears that the RH-enhanced kernel in RH7 won't
> > compile without it......
> >
--
jeff smith
---------------------------------------------------------------------------------
thought for the day: If something has not yet gone wrong then it
would ultimately have been
beneficial for it to go wrong.
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
