Arch Linux User Repository

Important update
I have updated and renamed some settings envvars. Please check your scripts, aliases, brain memory or whatever you use to store your build command and update them accordingly. Please read the description in the PKGBUILD file instead of the short summary in the pinned comment on the AUR or in the README in the repository as some important details important to this update are only found inside the PKGBUILD.

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

Repository URL
This package is hosted at sos!git. If you want to contribute to the package, you can do it here: https://git.staropensource.de/JeremyStarTM/aur-linux-clear

Issue handling
Please only submit issues in the package's repository if they aren't bug reports about the package or help requests. Please keep them to the AUR only. This prevents unnecessary signups.

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.

PKGBUILD environment variable customization
The PKGBUILD file supports customization via environment variables. Here's a list of all of them:
- _makemenuconfig: Invokes make menuconfig (ncurses-based default configuration menu) before compilation starts
- _makenconfig: Invokes make nconfig (ncurses-based nicer configuration menu) before compilation starts
- _makexconfig: Invokes make xconfig (X11-based GUI configuration menu) before compilation starts
- _reuse_current: Will use the configuration of the running kernel, if the running kernel is compiled with IKCONFIG_PROC
- _reuse_file: Will use the configuration file named kconfig contained in the PKGBUILD file's directory
- _update_kconfig_on_reuse: Specifies whether the kernel configuration shall be updated when using any of the 'reuse*' flags
- _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 open an issue
- _subarch: Specifies the subarchitecture to compile for (see the PKGBUILD file for a list of all subarches). Default is 41 (Generic x86-64), which is compatible with all amd64 processors. Must be a number
- _use_llvm_lto: Enables compilation with LLVM. Untested but should work. If not write a comment on the AUR.
- _subarch_microarch: Specifies the microarchitecture to compile for. Only applies to and is required by the GENERIC_CPU subarch. Must be a number between 1 and 4 (click for more information)
- _debug_kernel: Force enables kernel debugging options when set to y, force disables debug options when set to n or relies on the kconfig when unset
- _debug_script: Enables debugging for the PKGBUILD file

All of these variables just need to be set for them to apply, except for _subarch, _subarch_microarch and _debug_kernel. For more information please check their documentation inside the PKGBUILD file

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 command only needs to be executed once.

Build tool
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 file in a simple manner and decrease build time. And if you don't want that, using makepkg as-is works fine too.

What should I enter at localmodcfg?

I would like to use modprobed-db, so

_localmodcfg=~/.config/modprobed-db.conf ??

I tried and seems that it doesn't break anything.

@xuanruiqi You can try it if you want. If you followed the instructions in my pinned comment and it still for some reason doesn't work you can still just reboot to default kernel. It shouldn't break anything.

Thinking about installing this, but wanted to confirm that the extra boot parameters won't break other installed kernels.

@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.