Search Criteria
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: | 446 |
Popularity: | 3.17 |
First Submitted: | 2011-07-22 14:51 |
Last Updated: | 2021-04-17 10:20 |
Latest Comments
1 2 3 4 5 6 ... Next › Last »
graysky commented on 2021-04-14 15:06
@powerball253- Comments like this serve absolutely no purpose. In general, this package follows the progress of the official kernel which has bumped several times in the past week.[1] Further, no one is forcing you to rebuild a kernel you opted into using in the first place. Please don't spam the comments page with such statements.
graysky commented on 2021-04-02 13:32
@Kr1ss - Updated in 5.11.11-4, thanks.
Kr1ss commented on 2021-04-02 12:21
@graysky - Currently, building fails in environments with a modified
SRCDEST
folder. (EDIT/ For instance, mine is set to/tmp/makepkg/srcdest
)linux-ck-5.11.11-3-x86_64-prepare.log
:Hence I'd like to suggest a little patch :
Thank you, cheers !
artafinde commented on 2021-04-02 11:01
@graysky: Thanks already using it - noticed the PR from sirlucian :) Thanks!
graysky commented on 2021-04-02 10:05
@Zalgo - 5.11.11-3 should fix this. See the forum thread for discussion: https://bbs.archlinux.org/viewtopic.php?pid=1965531
graysky commented on 2021-04-02 10:05
@artafinde - with some help, the native option now works with Intel and AMD. You will have to select the correct option though:
Zalgo commented on 2021-04-02 07:20
Thanks for the tip :) If i figure out a way to fix the PKGBUILD that doesn't require manual untarring I'll pose it here
graysky commented on 2021-04-01 20:20
That's odd. Makepkg doesn't seem to be untarring the patch. If you do it manually and add that to the source array, it works as expected.
Zalgo commented on 2021-04-01 17:26
This currently fails on my system with
can anyone else reproduce? I'll test in a clean chroot
graysky commented on 2021-03-07 19:38
@artafinde - I need to dig deeper, but I think it will be difficult to assign a native CPU out of some configs.
For example,
X86_INTEL_USERCOPY
config. I do that now but no other AMD chips are listed by upstream[1].Further, I believe AMD chips should not be in the
X86_P6_NOP
config[2] orX86_CMOV
config[3].https://github.com/graysky2/kernel_gcc_patch/blob/master/enable_additional_cpu_optimizations_for_gcc_v10.1%2B_kernel_v5.8%2B.patch#L407
https://github.com/graysky2/kernel_gcc_patch/blob/master/enable_additional_cpu_optimizations_for_gcc_v10.1%2B_kernel_v5.8%2B.patch#L421
https://github.com/graysky2/kernel_gcc_patch/blob/master/enable_additional_cpu_optimizations_for_gcc_v10.1%2B_kernel_v5.8%2B.patch#L438