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.

xoita: Already noticed that yesterday when I was in bed, was too tired to fix it. Did it today, sorry for the small inconvenience.

krant: I have fixed the issue. It was a one line change. I didn't catch it as I had the necessary flag set to a different value, which is why the issue did not show up. I am sorry for the mistakes I've made over the last few months. I have previously had just little experience with kernel building (that however as improved thanks to maintaining this package). I unfortunately lack the motivation at times to extensively maintain this package, although I should have.

That now is history. What I however can promise for the future is that I'll setup a proper development branch for all the experimental "might not work" stuff and a stable (master) branch. In addition, I will test my changes. Thoroughly. And boot it. Maybe I'll let my CI runners on my instance build the kernel and run.

I've learnt from the dumb rookie mistakes. I don't want to do them again. Thanks however for sticking around for that long. I wish you happy holidays and a happy new year :)

It is not building anymore, I guess it's time to move on to another kernel where maintainers at least try to build what they are pushing to the people. Thanks @metak for all the fish, it was a good ride.

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.

krant: This seems to be a bug, I'll investigate it soon (hopefully before christmas)

Package no longer asks to select subarch, it just goes with the default. If do export _subarch=42 (to select Intel native) and then usual paru it still invokes gcc with -march=core2

KrisKorn: The package is designed to be built with your own kernel configuration, we do not ship one. You can supply one by renaming your .config file to kconfig and placing it next to the PKGBUILD file. If you want, you can set _copyfinalconfig to get your updated kconfig back.

I had two different problems:

1) I couldn't start virtualbox because the kvm module was set as built-in and not as a module. VirtualBox needs it to be a module to be able to remove it since it doesn't use it. The way to solve this was to enable the "${_makexconfig:="y"}" option and change the KVM option from there.

2) I also had to resort to makexconfig to disable NUMA support. I have a desktop computer that doesn't use NUMA so I thought I'd disable it. It would be nice to have the option to disable NUMA in the PKGBUILD file.

Thanks!

xoita: That is actually intended behaviour. This package will likely be built by regular users which have a working tty and therefore stdin. That's why it asks you if it is left blank. If automation or different behaviour is wanted, one can pass custom envvars. That's why they are there. Hope that explained it a bit.