AUR (en) - linux-ck

Git Clone URL:	https://aur.archlinux.org/linux-ck.git (read-only, click to copy)
Submitter:	graysky
Maintainer:	graysky
Last Packager:	graysky
Votes:	460
Popularity:	0.56
First Submitted:	2011-07-22 14:51 (UTC)
Last Updated:	2024-05-18 18:21 (UTC)

Latest Comments

« First ‹ Previous 1 .. 297 298 299 300 301 302 303 304 305 Next › Last »

ethail commented on 2011-08-20 11:01 (UTC)

@graysky: If I'm not wrong, chances are because flags and such is not area of my expertise, should the lines refering to KCFLAGS and KCPPFLAGS on the PKGBUILD be changed? They still point to the "old" configuration: make ${MAKEFLAGS} KCFLAGS="-march=native -O2 -pipe" KCPPFLAGS="-march=native -O2 -pipe" bzImage modules make KCFLAGS="-march=native -O2 -pipe" KCPPFLAGS="-march=native -O2 -pipe" INSTALL_MOD_PATH="${pkgdir}" modules_install

graysky commented on 2011-08-20 10:24 (UTC)

Bump to 3.0.3-3 Why? Pacman 3.5.4-4 just hit [core] and included a significant change to the CFLAGS. I am simply bumping to compile again with these new flags for the repo. AUR users should recompile after updated their systems AND modifying their /etc/makepkg.conf incorporating the changes in /etc/makepkg.conf.pacnew first!

graysky commented on 2011-08-20 09:14 (UTC)

@feilen - it's both. Look at line 173.

feilen commented on 2011-08-20 05:49 (UTC)

@graysky - Is it KCCPFLAGS or KCPPFLAGS? In the PKGBUILD it's KCPPFLAGS.

graysky commented on 2011-08-19 15:21 (UTC)

@misc - Right. The stock kernel PKGBUILD is compiled on a generic setup meant for generic i686 or x86_64 wheresa users of the AUR are likely not planning to make a generic package, but likely one for their hardware (particularly if march=native is used in the /etc/makepkg.conf). These flags are not the CFLAGS/CXXFLAGS defined in /etc/makepkg,conf rather, they are the KCFLAGS and KCCPFLAGS which are used in the compilation of the kernel. It is my understanding that with gcc >4.5 these are specific to the machine being used and will provide optimized code for said machine.