Hello David, hello all,
In theory, your are right:
> 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.
But at that special system, the newly-made bzImage failed to boot
so I had to rebuild it all from scratch as described.
Cheers,
Gerd
