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.

The past 3 versions of the linux-clear kernel have failed to build for me (it generally builds fine) with the following error message:

clang-15: error: optimization flag '-fivopts' is not supported [-Werror,-Wignored-optimization-argument]

clang-15: error: optimization flag '-fmodulo-sched' is not supported [-Werror,-Wignored-optimization-argument]

make[1]: *** [scripts/Makefile.build:252: scripts/mod/empty.o] Error 1

make: *** [Makefile:1286: prepare0] Error 2

==> ERROR: A failure occurred in build().

Aborting...

Built OK after I first manually compressed /lib/firmware/amd-ucode/microcode_amd_fam19h.bin into /lib/firmware/amd-ucode/microcode_amd_fam19h.bin.xz.

6.3.10-1 fails to build for me:

make[5]: *** No rule to make target '/lib/firmware/amd-ucode/microcode_amd_fam19h.bin.xz', needed by 'drivers/base/firmware_loader/builtin/amd-ucode/microcode_amd_fam19h.bin.xz.gen.o'.  Stop.
make[5]: *** Waiting for unfinished jobs....
make[4]: *** [scripts/Makefile.build:494: drivers/base/firmware_loader/builtin] Error 2
make[3]: *** [scripts/Makefile.build:494: drivers/base/firmware_loader] Error 2

@metak There is not any improvement on performance, just following arch's name pattern. Take packages in official repo as examples, linux package is 6.3.8-arch1-1, linux-zen package is 6.3.8-zen1-1-zen,linux-rt package is 6.3.0.11.realtime1-1-rt, linux-hardened is 6.1.33-hardened1-1-hardened. So personally I think we can use 6.3.8-clear1-1 or 6.3.8-clear1-1-clear to also follow this pattern. But I don't mind either way too, so it just depends you if change this kernel release name.

@k1gen Use 40 since llvm in arch repos is outdated and latest znver4 and emeraldrapids are not supported/detected unlike with gcc.

@ZhangHua What would be the benefit of that? I don't really mind either way...

hey @metak, there's this weird bug I have with _subarch=44: I was using _subarch=40 before, but with 6.3.8 I decided to reread the PKGBUILD, and I saw that MNATIVE_INTEL option is now 44, and not 40. so I did env _localmodcfg=y _subarch=44 _use_current=y _use_llvm_lto=y _debug=n paru -S linux-clear linux-clear-headers, and makepkg gets stuck, looping over the choice[1-41?]: 44 part. so what _subarch do I need to define for MNATIVE_INTEL optimizations?

@ZhangHua I personally like the current naming scheme more

Can you consider using 6.x.x-clear1-1 as the kernel release name instead 6.x.x-1-clear? I think the former is more like archlinux's name pattern.

@Moviuro Create your custom .config file and next time you're updating minor release use _use_current?

Launching makepkg with the following options: _subarch=13 _localmodcfg=1 makepkg -sriCfc will consistently bug me about modules that I don't want, and this has been going on for at least a dozen releases, e.g.:

BT8XX GPIO abuser (GPIO_BT8XX) [N/m/y/?] (NEW)

I really just want to answer always NO to those, how do I do that?