Package Base Details: linux-ck

Git Clone URL: (read-only)
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 395
Popularity: 1.282870
First Submitted: 2011-07-22 14:51
Last Updated: 2019-02-16 18:54

Packages (2)

graysky commented on 2011-08-23 20:14

@karabaja4 - dunno how -pf is including it since Paolo hasn't written it yet!

Det commented on 2011-08-23 15:11

@karabaja4, the latest BFQ patches I know of are here:

I don't think BFQ is yet updated for 3.0.

karabaja4 commented on 2011-08-23 10:59

Has BFQ been ported to kernel 3.0? Because I'm unable to see it anywhere, yet linux-pf 3.0 seems to have it included somehow...

graysky commented on 2011-08-22 23:31

Guess this is my 15 min...

Det commented on 2011-08-22 19:58

@graysky, did you see my post?

E: btw, and that *is* correct. Even Googling reveals that the only 2 hits for "KCCPFLAGS" in the whole internets are both here :).

Det commented on 2011-08-22 19:56

@graysky, did you see my post?

graysky commented on 2011-08-22 19:20

@feilen - perhaps a typeo on my part in the comment. In the PKGUBILD, I use the following:


I believe these are correct. Is this not the case?

feilen commented on 2011-08-22 18:11

@graysky That is still not what I'm talking about. Here, maybe this will make it more clear:
One of those two is the correct variable to use, but in one post you said KCCPFLAGS, while in the PKGBUILD it was KCPPFLAGS.

Det commented on 2011-08-21 20:30

@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).

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.

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:

$\O/> make help|grep modules_i
modules_install - Install all modules to INSTALL_MOD_PATH (default: /)

Anyway, thanks for telling about these KC(PP)FLAGS. I honestly always thought that makepkg.conf flags would always be used by default.

Anonymous comment on 2011-08-21 17:08

@Det and gravsyk: Thank you very much for your help! Det was right. My makepkg.conf is exactly like the one from you (gravsky), so it was upgraded the right way. Thank you very much for your help!