Package Base Details: linux-ck

Git Clone URL: (read-only)
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 400
Popularity: 3.496123
First Submitted: 2011-07-22 14:51
Last Updated: 2019-04-20 11:37

Packages (2)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 ... Next › Last »

zerophase commented on 2019-02-16 17:54

Is 4.20.10 giving anyone else compile errors?

gee commented on 2019-02-15 09:29

It probably is out of focus, but it would be really nice to add this patchset:

My boot takes 2 sec to test various raid6 algorithms, when I don't even use raid... Being able to specify the algorithm to use would shave that time off and be awesome.

air-g4p commented on 2019-01-17 07:23


Thanks for pointing out my non-Arch standard settings and I forgot there was a new /etc/makepkg.conf.pacnew hanging about. I'm back to standard now.

I see you removed 'subarch 27' from PKGBUILD, and now as expected, linux-ck-4.20.3-1-x86_64.pkg.tar.xz and its headers build without issue.

graysky commented on 2019-01-17 00:50

@air-g4p - As well, your CFLAGS are not the Arch standard... drop -fstack-protector-strong per the new makepkg.conf in pacman-5.1.2-2.

graysky commented on 2019-01-16 21:07

@air-g4p - See the comments in the PKGBUILD and the discussion here in the AUR.

<h1>Note - the march=native option is unavailable by this method, use the nconfig and manually select it.</h1>

In short, I do not know how to allow the native option to get set via the method used for the other discretely defined options.

air-g4p commented on 2019-01-16 20:35


I'm running an i7 8550U.

Under both /etc/makepkg.conf and ~/chroot/root/etc/makepkg.conf, I have these identical settings:


CARCH="x86_64" CHOST="x86_64-pc-linux-gnu"

-- Compiler and Linker Flags

CPPFLAGS="-D_FORTIFY_SOURCE=2" CFLAGS="-march=native -O2 -pipe -fstack-protector-strong -fno-plt" CXXFLAGS="-march=native -O2 -pipe -fstack-protector-strong -fno-plt" LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now"

-- Make Flags: change this for DistCC/SMP systems


-- Debugging flags

DEBUG_CFLAGS="-g -fvar-tracking-assignments" DEBUG_CXXFLAGS="-g -fvar-tracking-assignments"

Is there anything you see in my setup that would drive:

'The build fails with hundreds of instances of:

Support for P6_NOPs on Intel chips (X86_P6_NOP) [N/y/?] (NEW) 27'

that I mentioned when '_subarch=27' is set?

I normally build linux-ck in a clean chroot without issue, but this infinite loop issue disturbs me.

graysky commented on 2019-01-13 12:11

I remember looking at this a while ago and concluding it isn't possible... prove me wrong :)

air-g4p commented on 2019-01-13 09:37

Hi graysky,

I can confirm the build loop issue zoopp mentioned last month is still present in linux-ck 4.20.1-1.

With this PKGBUILD option set:

27. Native optimizations autodetected by GCC (MNATIVE)


The build fails with hundreds of instances of:

Support for P6_NOPs on Intel chips (X86_P6_NOP) [N/y/?] (NEW) 27

It appears to me that the only way out of this loop is crtl-c.

Of course, the build proceeds normally with any other appropriate subarch assigned.

graysky commented on 2019-01-12 09:38

@artafinde - ck1 disables NUMA

artafinde commented on 2019-01-12 09:32

@vltr: try enabling NUMA on ck.