Package Base Details: linux-ck

Git Clone URL: (read-only, click to copy)
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 421
Popularity: 4.48
First Submitted: 2011-07-22 14:51
Last Updated: 2020-01-20 21:18

Packages (2)

Latest Comments

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

timo_capa commented on 2019-10-12 12:21

I'm not sure if this is something you're interested in fixing, but compiling the kernel with Clang gets stuck at Installing boot image.... I'm assuming it's spamming something related to Kconfigs in the background related to GCC, as cancelling the build shows

"install: cannot stat '*'$'\n''* Restart config...'$'\n''*'$'\n''*'$'\n''* GCC plugins'$'\n''*'$'\n''Generate some entropy during boot and runtime (GCC_PLUGIN_LATENT_ENTROPY) [N/y/?] (NEW) ': No such file or directory"

E: Manually compiling a kernel from the tarball from works and boots.

Klotz commented on 2019-10-12 12:21

For version 5.2.21, I think applying the sed expression sed -i -re 's/(CFLAGS[[:space:]]+)\+=/\1:=/' to the ck stuff prior to patching will avoid a patch failure in tools/objtool/Makefile.

Pillgar commented on 2019-10-06 01:01

I'm getting DKMS errors when upgrading to linux-ck-ivybridge-5.2.19-1. On step (3/4) Install DKMS modules: Error! Bad return status for module build on kernel: 5.2.19-1-ck-ivybridge (x86_64).

It seems initcpio image can't build with any DKMS modules over ck-ivybridge-5.2.19-1

I'm using nvidia 435.21 dkms and vboxhost 6.0.12 dkms.

In make.logs I see error: incompatible gcc/plugin versions

I'm using gcc (9.1.0-2 updated: 2019-06-25)

Edit: There literally was just an update for gcc a few hours after I posted this. All solved.

Lessaj commented on 2019-09-15 19:14

It is building successfully now.

graysky commented on 2019-09-15 18:36

Please try 5.2.14-4

Lessaj commented on 2019-09-15 18:20

The addition of fix_patch-5.2-ck1_for_systemd-detect-virt_containers.patch seems to cause these last 3 lines to be dropped from kernel/sched/MuQSS.c even though they are in patch-5.2-ck1 which causes a build failure.



air-g4p commented on 2019-08-30 09:39

@graysky - It now appears the issue is exclusively related to modprobed-db. My latest build worked well in a clean chroot with ccache enabled, but I used an empty _localmodcfg= statement. Of course, the build time was quite lengthy, but it worked.

Any thoughts on a workaround, or a permanent fix?

Thanks for your help graysky....

graysky commented on 2019-08-28 18:41

@air-g4p - I do not use ccache so I cannot comment. I will say that builds using distcc on 5.2 fail where they worked fine with 5.1. Related? The change in the chroot build might be due to the modprobed-db change I made wherein the old behavior was to call it in recall mode via sudo which was always hacky in a PKGBUILD. The current method reads the database directly which the build scripts might not allow since your homedir is outside of the build root. Try building in the chroot without using the modprobed-db enabled; that will probably work.

air-g4p commented on 2019-08-28 13:08

@graysky - built without issue with ccache disabled, while running makepkg -sri so what is driving that fail?

Also, why did -ck previously build (many times) without issue in a clean chroot, but now it fails?


graysky commented on 2019-08-27 19:09

@air-g4p - Disable ccache and try again