Package Details: linux-ck-headers 6.11.10-1

Git Clone URL: https://aur.archlinux.org/linux-ck.git (read-only, click to copy)
Package Base: linux-ck
Description: Headers and scripts for building modules for Linux-ck kernel
Upstream URL: https://wiki.archlinux.org/index.php/Linux-ck
Licenses: GPL-2.0-only
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 459
Popularity: 0.199022
First Submitted: 2011-07-22 14:51 (UTC)
Last Updated: 2024-11-26 13:15 (UTC)

Latest Comments

« First ‹ Previous 1 .. 299 300 301 302 303 304 305 306 307 308 Next › Last »

Det commented on 2011-08-20 12:29 (UTC)

Shouldn't it be the choice of individual AUR users to rebuild their manually installed packages manually themselves anyway? E: my testing results show that the KC(PP)FLAGS are the ones set by the "Processor family" config option and they are added to the end of the gcc flag string already set by makepkg.conf. So it's unnecessary to define "-O2 -pipe" there - especially if the user has set "CONFIG_CC_OPTIMIZE_FOR_SIZE=y" (to use the '-Os' gcc flag instead of the default -O2).

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.

misc commented on 2011-08-19 14:45 (UTC)

Why would you change the flags at that point? The stock kernel pkgbuild merely has ${MAKEFLAGS} for the first and nothing for the second line.

« First ‹ Previous 1 .. 299 300 301 302 303 304 305 306 307 308 Next › Last »