I'm getting in a muddle over Kernel pkgbuilds ...
I'm building 2.6.14-archck5 (custom)
should it not be in 2.6.14-archck5 ?
Thing is the way I see it is that kernels custom built are still going into linux-<2.6.X> & vmlinuz26 surely this is wrong
should I add
mv $startdir/src/linux-$basekernel $startdir/src/linux-$basekernel-archckX
I want kernel to be seperate from stock kernel not replace it ....
emmm torn between stock arch kernel PKGBUILD or archck version (which does not include mkinitrd!) ((atm!!!))
Man its been a long while since I built a kernel lol have forgotten everthing now I remember why I stopped building them ,,,,,,
emm Whats this all about ???
LOCALVERSION is set in .config. In current package is -ARCH. Usually for custom builds it´s -CUSTOM.
I'm trying to get pgkbuild to install to linux-<kernel version>-<patch> (not pkg though cannot use 2 '-'!)
Have added <patch> to kconfig etc ...
Wiki pkgbuild was not much help stock Arch may be better but not for 64 lol
Archck pkgbuild is different again (no mkinitrd!)
np I'll keep going
Phrakture will help me out becuase he is my friend 8)
You´re building for Arch32 or Arch64? For Arch64 you could build up on my testing kernel. Good luck.
Usually for custom builds it´s -CUSTOM.
You mean that's what you usually use? You can use what you like, there is no "usually" about it!
Mr Green - the custom kernel wiki page explains in great detail how the PKGBUILD works, make sure you read it properly. The PKGBUILD on the wiki is generic and the PKGBUILDs for archck etc are not, they are specifically tailored to that kernel as somethings will never change for it, like the location of the modules. A good thing to do would be to diff several kernel PKGBUILDs, then you can see where changes were made and why
Thanks for that .... I think initrd changes are confusing me a little (I'll get over it!!)
Read the wiki :shock: ok ok ....
Errr I'm trying to build archck5 for arch64 atm ...
I figure it out when I get sober hic!!
Have a Great Xmas ;-)
Thanks for all the fish