[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: do I really need "make-kpkg clean"?

Apparently, _Jon Dowland_, on 05/02/2005 07:49 AM,typed:
On 5/1/05, H. S. <greatexcalibur@yahoo.com> wrote:


I am compiling a new kernel and tinkering with various options. If I
just compiled a new version and just want to make slight changes in it,
do I really need to do "make-kpkg clean" and wait an hour before I get a
new one?

To try and answer your question: some other posters have indicated
situations where it is necessary to rebuild the whole kernel, version
numbering etc.

However there are kernel tweaks that you can perform which don't
require the objects to be rebuilt (or, those that do, the Makefile can
work out for you), and it would be nice to avoid building everything

However, make-kpkg clean does more than just delete the object files,
it also cleans up some debian state stuff (.stamps etc.) which
unfortunately you do need to do on every rebuild. It may be possible
to ask make-kpkg to not call the master 'make clean'.

In some circumstances, when enabling a single module for example, I
may skip make-kpkg and copy the resulting kernel object file into
/lib/modules manually, then run depmod -a. This seems to work less
often with the 2.6 kernel as there are so many more module

In my case, I am pitting my head against the problem of getting a framebuffer to work to get the tux logo on bootup. To do so, I compiled my version of kernel, let us call is 2.6.11.myver, and included the framebuffer support, logo support, etc. But didn't get the logo, just some blank screen for 10 or so seconds and then the normal bootup message. Now, going through google, I am trying out various options, e.g. to disable bitblitting, to include a certain card module, etc. To do these tweaking, I was booting in to a different version (2.6.10) and running:
#> make menuconfig (to tweak options)
#> fakeroot make-kpkg --append-to-version=.myver --initrd kernel_image

So far, this has seemed to work (note there is no "make-kpkg clean" here).

Basically, I am recompiling exactly the same version kernel but with some tweaking of the config file.

From your comments, I understand that I must run "make-kpkg clean". Am I correct?

(Remove all underscores,if any, from my email address to get the correct one. Apologies for the inconvenience but this is to reduce spam.)

Reply to: