On Thu, Sep 16, 1999 at 08:01:03AM +0200, Gerd wrote:
: > I see this advised an awful lot, but I've never understood why people
: > insist on re-building dependencies and recompiling the kernel from scratch
:
: Yes, AFAIK this hint is included in related documentation. If the
I'm thinking that this is more for the benefit of newbies than
anything else. It's probably less headache for everyone if you
just tell the new people to start over from scratch instead of
describing to them the 'make' process and enumerating the cases
where it's not terribly necessary.
I don't quite understand what problem you were encountering
doing the same thing, but when I go from a "make zImage" to "make
bzImage" after encountering a "too big" error, the compilation
always zips through the directories without actually doing
anything (why should it? -- everything's already compiled) and
simply constructs a bzImage file instead of zImage. I've done
this for every kernel I've ever compiled (that needed it; several
dozen). The only mention of "*zImage" in the kernel's makefiles
are in the arch/* areas, which appear to only contain commands
performed at the very tail end of the compilation process.
Thus, specifying zImage/bzImage should have zero effect on any
compilation done prior to this point.
*shrug*
AFAIK, the only time a true complete rebuild is necessary is when
source code has been modified. I believe even the newer kernels
detect configuration changes and know to rebuild only the affected
chunks of code while leaving everything else untouched.
Corrections are welcome. I'm just trying to save everyone some
unnecessary work...
Cheers,
David
--
== David Nesting WL7RO Fastolfe [EMAIL PROTECTED] http://fastolfe.net/ ==
