Package Details: linux-ck-headers 6.11.10-1

Git Clone URL: https://aur.archlinux.org/linux-ck.git (read-only, click to copy)
Package Base: linux-ck
Description: Headers and scripts for building modules for Linux-ck kernel
Upstream URL: https://wiki.archlinux.org/index.php/Linux-ck
Licenses: GPL-2.0-only
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 459
Popularity: 0.129775
First Submitted: 2011-07-22 14:51 (UTC)
Last Updated: 2024-11-26 13:15 (UTC)

Latest Comments

« First ‹ Previous 1 .. 57 58 59 60 61 62 63 64 65 66 67 .. 308 Next › Last »

artafinde commented on 2017-12-18 07:58 (UTC)

@graysky I suggest for now to delete the 24 option (line #38) on the PKGBUILD. If a user wants native detection let him go through makepkg.

foi commented on 2017-12-18 06:16 (UTC)

Hi!

Failed in install (distro: manjaro gnome):

==> Verifying source file signatures with gpg... linux-4.14.tar ... FAILED (unknown public key 79BE3E4300411886) patch-4.14.7 ... FAILED (unknown public key 38DBBDC86092693E) ==> ERROR: One or more PGP signatures could not be verified! ==> ERROR: Makepkg was unable to build linux-ck.

air-g4p commented on 2017-12-18 05:41 (UTC)

Hi graysky,

Thank you very much for attention and extremely quick correction of this issue. Highly impressive, indeed!

When I get a chance, I'll try a re-build with the current release, and let you how things went.

All the best,

air|g4p

graysky commented on 2017-12-17 23:33 (UTC) (edited on 2017-12-17 23:34 (UTC) by graysky)

@artafinde - Short of applying this patch and shipping the corresponding config (which makes building for repo-ck more difficult), I don't know how to cover that use-case.

It might be a bit of a hassle for you, but if you just run makepkg -s outside of the chroot, setup the config to your liking, you can replace the shipped config with config.last and update the checksums before you build in the chroot.

artafinde commented on 2017-12-17 23:23 (UTC)

@graysky: if you choose 24 (native) then you are asked again for P6_NOPS which fails to auto-configure with "yes" Support for P6_NOPs on Intel chips (X86_P6_NOP) [N/y/?] (NEW)

graysky commented on 2017-12-17 09:56 (UTC)

@air-g4p - Yes, the failure is due to user intervention being required to select a sub-arch. Please try 4.14.16-3 in which the _subarch variable should take care of this use case.

air-g4p commented on 2017-12-17 06:21 (UTC)

Hi graysky,

In the event you are not aware, your linux-ck 4.14.6-2 AUR fails to build in a clean chroot, using: extra-x86_64-build.

Your immediately prior release also failed to build using either extra-x86_64-build or makechrootpkg -c -r $CHROOT.

We know for a fact your AUR is broken because when discussing this linux-ck build failure on #archlinux, another experienced AUR user also replicated the same extra-x86_64-build failure on his system.

I have pasted my entire build run for your review at: https://bpaste.net/show/3c5c3d9ea326. That paste URL will remain valid for one month.

Additionally, for those users willing to employ this approach, I can confirm your AUR can be successfully built and installed with: makepkg -si.

I hope you are able to determine, and correct, whichever part(s) of your code is/are causing the build failure, as many of us strongly prefer to build AURs exclusively within a clean chroot environment.

Thank you for providing an otherwise excellent alternative kernel. Your effort is immensely appreciated.

Cheers,

air|g4p

eduardoeae commented on 2017-12-16 12:48 (UTC)

Works OK now. Thanks!

graysky commented on 2017-12-16 11:36 (UTC)

@edu and sha - Please try now.

Shaikh commented on 2017-12-16 08:03 (UTC)

I encountered the same problem as @eduardoeae.

« First ‹ Previous 1 .. 57 58 59 60 61 62 63 64 65 66 67 .. 308 Next › Last »