Arch Linux User Repository

Proposal update
As I have recently announced, I proposed moving this package's source to my own Forgejo (git forge) instance and creating a push mirror to the AUR. As I haven't received any feedback on the proposal, I will be moving forward and move the repository in the next package update. Again, nothing should change, just where the changes are pushed to. I hope that this change will provide an easier way of contributing (AFAIK there isn't a way to contribute to a package directly or I'm just dumb).

Information comment
This comment provides useful information about this package. Make sure to read it through, you won't regret it.

Updates
I usually publish updates 0-3 days after a kernel release, depending on how busy I am.
If I however get wind of security-relevant updates or any vulnerabilities I will try to update the kernel as soon as possible and write a comment about the vulnerability/update. So make sure to subscribe to this package's comment mailing list.

The PKGBUILD supports customization via environment variables. Here's a list of all of them:
_makemenuconfig: Invokes make menuconfig (default configuration menu) before compilation starts
_makenconfig: Invokes make nconfig (nicer configuration menu) before compilation starts
_makexconfig: Invokes make xconfig (GUI configuration menu) before compilation starts
_use_current: Will use the configuration of the running kernel, if the running kernel is compiled with IKCONFIG_PROC
_copyfinalconfig: Copies the final kernel configuration into the repository root as kconfig-new before compilation starts
_localmodcfg: Only compiles modules found in modprobed-db's database (which decreases compilation time and kernel size)
_use_llvm_lto: Compiles the kernel with LLVM instead of GCC. Should work, if not write a comment
_subarch: Specifies the sub architecture to compile for (see the PKGBUILD file for a list of all subarches). Default is 40 (Generic-x86-64), which is compatible with all amd64 processors. Must be a number
_debug: Force enables debug options when set to y, force disables debug options when set to n or uses the config defaults when unset

All of these variables just need to be set for them to apply, except for _subarch and _debug. See their descriptions for more information.

If you want a dead simple way to compile this package, you can try out my build tool. It includes a few no nonsense changes to the kernel configuration and allows you to configure the PKGBUILD in a simple manner and decrease build time. And if you don't want that, using makepkg as-is works fine too.

GPG errors
If makepkg complains about invalid PGP keys, try running this command first: gpg --locate-keys torvalds@kernel.org gregkh@kernel.org sashal@kernel.org benh@debian.org. This only needs to be done once.

@metak works like a charm on both local and building machine. thanks m8.

@bruceutut Edit: Hey brucetut. I rearranged some things in pkgbuild file and now it appears to build fine. ;-) Can you try it and report back. (I won't bump pkrel for this)

@metak

Here is the full build log on building machine built with extra-x86_64-build

https://fars.ee/W-yp.log

And built package with issue:

https://build.archlinuxcn.org/~bruceutut/linux-clear-tesonly.pkg.tar.xz

And same package built with makepkg on my local machine:

https://build.archlinuxcn.org/~bruceutut/linux-clear-4.20.8-1-x86_64.pkg.tar.xz

And my friend another aur packager try to modify pkgbuild to solve this issue refering ths

https://fars.ee/XYbb
https://build.archlinuxcn.org/~megumifox/linux-clear/PKGBUILD

Thanks again.

@bruceutut I'll try replicating this issue when I get some free time, but in the meantime, you could upload full build logs and the built 'bad' package somewhere for me to take a look.

@metak

Actually, I can build correct package using makepkg command. Or yay/pikaur something.

But the bad package using extra-x86_64-build command, on local machine or my building machine.

The bad package does not have crypto_user and xz compression module is not enabled as well.

Thanks for your patience :)

@bruceutut crypto_user should be built since this pkgbuild enables it. It's in /usr/lib/modules/4.20.6-1-clear/kernel/crypto/crypto_user.ko.xz, both on my local build and in clean chroot for repo.
Have you checked your build log? You haven't provided any info.

crypto_user module not found in package after successful build.
Anything am i doing wrong ?

@metak Yes, after turbo3 patch is removed the package can be built again. :) I have also left this comment in the github.

@enihcam That's probably due to the patch turbo3-scheduler.patch in latest commit. No problems on my machine or in repo build. You can try building with that patch disabled to check?

ld: kernel/sched/fair.o: in function select_task_rq_fair': fair.c:(.text+0x61a): undefined reference tobest_core' ld: fair.c:(.text+0x628): undefined reference to `second_best_core' make[1]: [Makefile:1032: vmlinux] Error 1 make: [Makefile:1001: autoksyms_recursive] Error 2 ==> ERROR: A failure occurred in build(). Aborting... ==> ERROR: Makepkg was unable to build linux-clear. ==> Restart building linux-clear ? [y/N] ==> ------------------------------------

4.19.3-1 has no such problem.