Re: do I really need "make-kpkg clean"?
On 5/1/05, H. S. <firstname.lastname@example.org> 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
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