On Thursday 23 April 2009 07:43:20 Xavier Parizet wrote: > I think the MAKEOPTS was not the problem, but only the make prepare... I > remember to see before that "sometimes", the kernel source tree is no > more up-to-date with the last kernel build, so when i see that problems, > the first thing to do is to make mrproper && make oldconfig && make > prepare to get a clean up-to-date kernel build tree.
I don't like the sound of that; it's distinctly ominous. What can interfere with the kernel source tree after I've compiled a kernel, copied it to the boot partition, booted it and moved on to other things? One or two packages install modules into the source tree, but at the moment I can only think of the one I was working on: nvidia-drivers. Or is it that compiling the kernel itself damages its own source configuration? -- Rgds Peter
