Search Criteria
Package Base Details: linux-ck
Package Actions
Git Clone URL: | https://aur.archlinux.org/linux-ck.git (read-only, click to copy) |
---|---|
Submitter: | graysky |
Maintainer: | graysky |
Last Packager: | graysky |
Votes: | 461 |
Popularity: | 0.97 |
First Submitted: | 2011-07-22 14:51 (UTC) |
Last Updated: | 2024-03-16 18:02 (UTC) |
Latest Comments
« First ‹ Previous 1 .. 20 21 22 23 24 25 26 27 28 29 30 .. 305 Next › Last »
graysky commented on 2019-10-30 20:11 (UTC)
Should be there as a module. Building wireguard-dkms on CK works for me:
Kr1ss commented on 2019-10-30 19:41 (UTC)
FWIW, I'm also setting that option manually, hence I'd support @air-g4p's request. Thx again for maintaining this btw !
Cheers !
air-g4p commented on 2019-10-30 19:36 (UTC)
@graysky - wireguard-dkms failed to build on CK with this output:
http://ix.io/20kT
I asked the devs at #wireguard about this failure, and was told I needed to enable: CONFIG_NET_FOU
(FOU = foo over udp)
After enabling that and rebuilding linux-ck --> Success.
Per Jason's (zx2c4), the lead wireguard dev, suggestion, can you please enable CONFIG_NET_FOU by default on linux-ck?
Thanks graysky
graysky commented on 2019-10-27 14:46 (UTC) (edited on 2019-10-29 20:42 (UTC) by graysky)
@timo - OK... that is likely because your .config got tweaked due to your CC= line. I opened a flyspray shown below. See it for a solution: https://bugs.archlinux.org/task/64315
timo_capa commented on 2019-10-27 14:03 (UTC)
@graysky What I did was add
CC=clang
before make in the PKGBUILD to use Clang as compiler.What worked was using makepkg for compiling till it gets stuck, and then end it with make modules_install and make install from the src folder. Doesn't give a package for pacman, but works.
I've tried linux-pf the same way, though that got stuck at the same place :)
graysky commented on 2019-10-27 12:34 (UTC)
@simona - the recent failure of dkms is due to the fact that there are both a newer version of the toolchain and of the dkms packages in [testing] currently. The advice I have been given is that it always a good idea to build the kernel against [testing] to prevent version mismatch errors when toolchain packages come out of [testing] and into [core].
I need to figure out what the best option is now.
@timo_capa - I am not sure how you go about building in Clang... I am using the official Arch devtools for clean chroot building. Are you patching the kernel source with ck1?
simona commented on 2019-10-27 11:52 (UTC)
==> dkms install vboxhost/6.0.14_OSE -k 5.3.7-1-ck-skylake Error! Bad return status for module build on kernel: 5.3.7-1-ck-skylake (x86_64)
timo_capa commented on 2019-10-12 12:21 (UTC) (edited on 2019-10-12 14:43 (UTC) by timo_capa)
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 kernel.org works and boots.
Klotz commented on 2019-10-12 12:21 (UTC)
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.« First ‹ Previous 1 .. 20 21 22 23 24 25 26 27 28 29 30 .. 305 Next › Last »