Arch Linux User Repository

The PKGBUILD supports customization via environment variables. Here's a list of all of them:
_makemenuconfig: Invokes make menuconfig (default configuration menu) before compilation starts
_makenconfig: Invokes make nconfig (nicer configuration menu) before compilation starts
_makexconfig: Invokes make xconfig (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
_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 write a comment
_subarch: Specifies the sub architecture to compile for (see the PKGBUILD file for a list of all subarches). Default is 40 (Generic-x86-64), which is \compatible with all amd64 processors. Must be a number
_debug: Force enables debug options when set to y, force disables debug options when set to n or uses the config defaults when unset

All of these variables just need to be set for them to apply, except for _subarch and _debug.

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

Kernel has been updated and is now maintained again.

Thank you metak for creating this package in the first place.

@Tjuh the documentation for kernel params can be found here:

https://www.kernel.org/doc/html/v5.6/admin-guide/kernel-parameters.html

I think it would be helpful to get some descriptions on those kernel parameters. What do they do and why are they usefull to have. I know some of them like - quiet, rootfstype and rw - but I'm unfamiliar with the rest.

I understand. Thank you.

@Tjuh That's because of gcc10 in testing repo that you're using? You can check in arch linux's repo all the commits related to gcc10 warnings.
Clear Linux still uses gcc9 so we'll see when they'll update that.

==> Starting build()...
scripts/kallsyms.c: In function ‘read_symbol’:
scripts/kallsyms.c:222:2: warning: ‘strcpy’ writing between 1 and 128 bytes into a region of size 0 [-Wstringop-overflow=]
  222 |  strcpy(sym_name(sym), name);
      |  ^~~~~~~~~~~~~~~~~~~~~~~~~~~
arch/x86/kvm/../../../virt/kvm/kvm_main.c: In function ‘__kvm_gfn_to_hva_cache_init’:
arch/x86/kvm/../../../virt/kvm/kvm_main.c:2236:42: error: ‘nr_pages_avail’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
 2236 |  for ( ; start_gfn <= end_gfn; start_gfn += nr_pages_avail) {
      |                                ~~~~~~~~~~^~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
make[2]: *** [scripts/Makefile.build:267: arch/x86/kvm/../../../virt/kvm/kvm_main.o] Error 1
make[1]: *** [scripts/Makefile.build:505: arch/x86/kvm] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:1683: arch/x86] Error 2
make: *** Waiting for unfinished jobs....
kernel/bpf/core.c: In function ‘bpf_patch_insn_single’:
cc1: warning: writing 8 bytes into a region of size 0 [-Wstringop-overflow=]
In file included from kernel/bpf/core.c:21:
./include/linux/filter.h:550:20: note: at offset 0 to object ‘insnsi’ with size 0 declared here
  550 |   struct bpf_insn  insnsi[0];
      |                    ^~~~~~
==> ERROR: A failure occurred in build().
    Aborting...

No problem with previous iteration, but this one fails.

@metak I see, thanks. @lucasrizzini thanks.

@rvlobato As @lucasrizzini has said, you can easily add that patch and build it for your self. I removed fsync patch because clear team don't feel comfortable enough to include it.

No. You have to patch the source manually. Just add "patch -Np1 -i /path/to/patch/file" just below "### Add Clearlinux patches" around line #108.

Patch -> https://git.covolunablu.org/portaloffreedom/linux-covolunablu-gaming/blob/master/futex-wait-multiple-5.2.1.patch

Hello, is fsync still working on linux-clear?

@metak Thanks.