I do not know how much this issue can be discussed here. But I had one problem with the compilation of the kernel (and it doesn’t want to be solved in any way). The kernel persistently creates sizes larger than the standard. I already disconnected everything that I thought was unnecessary. And in modules brought everything that could be necessary. And clearly there is no debag. The core size has slightly decreased, but still continues to remain within 3-plus meg (with a strip, the last core came out at 2.5 mega. Compare with the standard - 2.1 mb). Naturally. I can not put such a kernel - lilo swears, he says, very big.

  • make mrproper for cleaning do not forget.
  • Compilation options CFLAGS = '- O2 -march = native -fomit-frame-pointer'
  • But I don’t know how to attach the kernel config itself here. Just throw in the text - there will be a huge footwoman.

Once even the entire folder was demolished, unfolded again. Anyway, with the same configs, the same result comes out ... 3-4 mega cores :( I can not understand anything ...

  • For the archive: altlinux.org/KernelBuild (in short - this is still not required, lilo works perfectly with the regular kernel; see, for example, jeter starter). - Michael Shigorin

1 answer 1

The output is vmlinux or vmlinuz. If vmlinux can try to compress during compilation. make bzlilo.

  • Well, as I understand it, make itself already creates vmlinux, a compressed algorithm that was specified in the configuration file. - Zulan
  • I can be mistaken, but earlier make created a kernel without compression. - andrey_sn
  • So it turned out ...: (confused by the similarity of the names vmlinux and vmlinuz. In addition, the compressed bZimage itself was stuck deep into the tree and the brain never looked for it ... - Zulan