Package Base Details: 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.70
First Submitted: 2011-07-22 14:51 (UTC)
Last Updated: 2024-05-08 19:04 (UTC)

Latest Comments

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

graysky commented on 2011-08-20 18:41 (UTC)

@feilen - /etc/makepkg.conf contains CFLAGS and CXXFLAGS while the PKGBUILD contains KCFLAGS and KCPPFLAGS. Makepkg will automatically set the CFLAGS and CXXFLAGS from /etc/makepkg.conf when you invoke it. It's redundant to echo them again prior to the make steps.

feilen commented on 2011-08-20 18:20 (UTC)

That's what I was looking at. You said in a previous post KCFLAGS and KCCPFLAGS and the PKGBUILD has KCFLAGS and KCPPFLAGS.

graysky commented on 2011-08-20 17:03 (UTC)

@Lothium - that's really odd. The files in question can be found here: http://projects.archlinux.org/svntogit/packages.git/tree/pacman/trunk

<deleted-account> commented on 2011-08-20 15:59 (UTC)

Mmmh... I updated to the latest pacman, but I have no makepkg.conf.pacnew... What I have to do?

graysky commented on 2011-08-20 13:52 (UTC)

@ethail - my bad! Bump to -4 @Det - I don't understand your question... do you feel that I'm forcing users to rebuild by bumping the PKGBUILD?

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!

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