Arch Linux User Repository

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
- _use_current: Will use the configuration of the running kernel, if the running kernel is compiled with IKCONFIG_PROC
- _optimize_defconfig: Applies package maintainer-picked configuration changes to your defconfig. Only takes effect with _use_current being enabled
- _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/MGENERIC_CPU (Generic x86-64), which is compatible with all amd64 processors. Must be a number or subarch name
- _subarch_microarch: Specifies the microarchitecture to compile for. Only applies to and is required by the MGENERIC_CPU subarch. Must be a number between 1 and 4 (click for more information)
- _debug: Force enables debug options when set to y, force disables debug options when set to n or uses the config defaults when unset
- _show_compile: Enables verbose-er compilation output and displays all executing make targets. Enabled by default, unset for 'pv' output

All of these variables just need to be set for them to apply, except for _subarch and _debug. 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.

OK, turning debug info off works.

(Maybe because I have CONFIG_DEBUG_INFO_BTF turned on in my kernel config which causes resolve_btfids to be called during DKMS build. Let me try turning most debug options off.)

@xuanruiqi After testing nvidia-dkms I couldn't reproduce it. It builds fine (gcc & llvm). It's definitely something on your system that's causing this. Try building in clean environment?

I was building nvidia-dkms. Some modules like nvidia need btf info to build properly, so maybe you want to put it under an option or something like that. AFAIK a lot of people use nvidia-dkms.

@xuanruiqi I had to comment out that line in PKGBUILD file when I synced it with stock arch because it would fail to build. (not enabled on Clear) It needs some other debugging things enabled like CONFIG_DEBUG_INFO, CONFIG_DEBUG_INFO_BTF, CONFIG_PAHOLE_HAS_SPLIT_BTF which will increase the size and compilation time. I can enable the debug info if others want it, but I would rather not.

As for dkms error, I just tried building random module (rtl88x2bu) and it builds fine. (gcc & llvm) Please specify which module/versions, etc. (whole build log)

SOLUTION: please fix the PKGBUILD, add this line, otherwise external DKMS modules can't be built:

install -Dt "$builddir/tools/bpf/resolve_btfids" tools/bpf/resolve_btfids/resolve_btfids

See diff in official linux package commit history.

Hey all! With LLVM compiled kernel (5.16.2), I get this error when I try to compile DKMS modules:

/bin/sh: line 1: ./tools/bpf/resolve_btfids/resolve_btfids: No such file or directory

This error is absent in linux-clear <=5.16.1.

GCC doesn't work either. I suspect this is a really silly mistake, but I can't fix it...

@metak Thank you!

@k0r0ng It's not enabled by default in CLR config file, I've enabled it in ˙5.15.14-1˙.

Why CONFIG_KPROBES not included by default?

@metak @Moviuro You're both legends. Compiling on Skylake for Atom with single short script now, no interaction required. Thank you so much!

@metak I can confirm that 5.15.7-3 and 5.15.7-4 changes work fine here! Happy to use clang kernel with new dkms support :)