Do you already have the config file ? If so make mrproper
make xconfig (or whatever your fav configurator is) then choose load config from file, and type in the file name when prompted. (the config file can be anywhere doesn't have to be in the kernel dir) Save and exit now your make dep and the rest of the build process should work. Regards, Adam On Wed, 2002-11-20 at 21:33, Michael Tiernan wrote: > Okay, I have to ask this.... I feel stupid but I've not seen the answer yet. > (No doubt as soon as I send this I'll figure it out.) > > If I take the kernel sources (/usr/src/linux*) and do a "make mrproper" to > clean them up/out, I end up with a "blank slate". This works fine. > > Now, if I copy a config from the configs directory to be ".config" (or if I > used a config file from another build) what's the *next* step to be done? > > Using 'make dep' fails. Doing a 'make config' doesn't do as I'd expect. > Also, doing a 'make oldconfig' doesn't seem to take use the '.config' file as > gospel and makes changes to it. > > So what's the deal, does a '.config' file represent ALL the needed > switches/options to create a new kernel? I guess some of what I'm looking > for here is reproducability. > > Anyone got any thoughts on this? > (Or a manual for me to RTFM?) > > Thanks for your time. > > > > -- > redhat-list mailing list > unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe > https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
