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

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.

@seqfault Sorry, I barely have any free time to update the packages these days. Can you just install linux-clear binary from my repo and see if it boots?

@metak? there's no issue tracker in upstream repo, can you help me?

forget about not being able to compile with llvm18, I can't boot into 6.6.3 at all. the system freezes on gdm with blinking caps lock light, here's journalctl -b -1: https://0x0.st/HxN4.txt. linux-hardened works fine

Edit: Merged! Thanks @metak

Heres a patch to fix clang lto compiling only modifying the PKGBUILD https://gist.github.com/xstefen/546d201257475c0ffbb954369453f692

@seqfault I don't know since I don't run any benchmarks/tests. Upstream Clear team tests and develops with gcc in mind so I can't say anything about clang/llvm.

@metak thanks for explaining! how do you think, what will produce faster kernel binary: llvm16 without patch 162 but with lto, or gcc13 without lto, but with 162 optimizations?

@seqfault Hi. Those two optimization flags are not supported by clang/llvm. 1
gcc-lto is not yet supported by kernel, there are some patches, but I haven't looked into it. 2 3
You should use _subarch=44 now since llvm16, but only initial support was added for znver4.

hey @metak, now that llvm16 is in the stable repos, can we compile this with patch 162? if not, is there a way to build with gcc, but still have lto? also, should I use _subarch=44 now instead of 40, if using llvm16?

@tydynrain llvm/clang is unsupported upstream, comment out the latest patch Patch0162: 0162-extra-optmization-flags.patch.