Check out the Pastebin Gadgets Shop. We have thousands of fun, geeky & affordable gadgets on sale :-)Want more features on Pastebin? Sign Up, it's FREE!


By: a guest on Aug 24th, 2011  |  syntax: None  |  size: 1.02 KB  |  views: 64  |  expires: Never
download  |  raw  |  embed  |  report abuse  |  print  |  QR code  |  clone
Text below is selected. Please press Ctrl+C to copy to your clipboard. (⌘+C on Mac)
  1. @graysky, hehe, seems like makepkg.conf flags don't affect the size image of my kernel image after all. My stupid ego is having problems dealing with this (or at least was having).
  3. Well, moving on. The '-O2' flag messes up "CONFIG_CC_OPTIMIZE_FOR_SIZE=y" (-Os) (funnily even resulted in a 96 bytes bigger kernel for me - 300 KiB smaller after removing '-O2') so at least that should be removed as it's default anyway. In addition as told in FS#11864, "-fstack-protector" has been enabled already in the kernel for a long time: I even tested both of these just to make sure.
  5. The KC(PP)FLAGS aren't needed in the package() function either since there's no compiling done there anyways. That line only installs the already built modules into the correct place:
  7. $\O/> make help|grep modules_i
  8. modules_install - Install all modules to INSTALL_MOD_PATH (default: /)
  10. Anyway, thanks for telling about these KC(PP)FLAGS. I honestly always thought that makepkg.conf flags would always be used by default.
clone this paste RAW Paste Data