> -----Original Message----- > From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list- > bounces@xxxxxxxxxx] On Behalf Of Eric Sisler > Sent: Sunday, January 29, 2006 5:52 AM > To: General Red Hat Linux discussion list > Subject: Re: Red Hat Kernel Sources > > On Sat, 2006-01-28 at 13:53, Greg Golin wrote: > > > How many of you have been able to compile a kernel from redhat sources > > without a problem? I don't think I've ever done it successfully. I > > consistently run into the same problem, make modules errors out on > > something. I go and disable that something and try again, at which > > point make modules fails with something else, goto 10. Eventually I > > run out of patience and go look at something shiny. Never had a > > problem with kernel.org kernels though. Is there something I need to > > do beyond the make oldconfig/make bzImage/make modules/make > > modules_install? > > Been compiling them for years. I usually do "make menuconfig" or "make > xconfig" as I'm trying to add/remove something specific. My process is: > > make mrproper > make [menuconfig|xconfig] > make dep > make clean > make bzImage > make modules > make modules_install > > -Eric > > -- > > Eric Sisler <esisler@xxxxxxxxxxxxxxxxxxxxx> > Library Applications Specialist > Westminster Public Library > Westminster, CO USA > If you want to make any changes to the default kernel configuration you should take note that 'make mrproper' would clear such changes (it would delete the file '.config' which contain the configuration). Therefore, if you have already made any configuration changes via menuconfig or xconfig you should either do not issue command 'make proper' or backup .config somewhere before that command and restore after that command. Actually, 'make mrproper' command is usually needed only after unsuccessful kernel builds when 'make clean' does not restore the correct source tree state - such an incorrect state may be the reason of errors during compilation (usually those errors relate to files' dependencies). Usually, 'make clean' is enough to wipe the files created or modified by the unsuccessful build attempt and restore correct state. Alexey Fadyushin Brainbench MVP for Linux http://www.brainbench.com -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
