Arch Linux User Repository

Please, check new release. You have now several variables to enable/disable features.

References:

##
## The following variables can be customized at build time. Use env or export to change at your wish
##
##   Example: env _microarchitecture=99 use_numa=n use_tracers=n use_pds=n makepkg -sc
##
## Look inside 'choose-gcc-optimization.sh' to choose your microarchitecture
## Valid numbers between: 0 to 99
## Default is: 0 => generic
## Good option if your package is for one machine: 99 => native
if [ -z ${_microarchitecture+x} ]; then
  _microarchitecture=0
fi

## Disable NUMA since most users do not have multiple processors. Breaks CUDA/NvEnc.
## Archlinux and Xanmod enable it by default.
## Set variable "use_numa" to: n to disable (possibly increase performance)
##                             y to enable  (stock default)
if [ -z ${use_numa+x} ]; then
  use_numa=y
fi

## For performance you can disable FUNCTION_TRACER/GRAPH_TRACER. Limits debugging and analyzing of the kernel.
## Stock Archlinux and Xanmod have this enabled. 
## Set variable "use_tracers" to: n to disable (possibly increase performance)
##                                y to enable  (stock default)
if [ -z ${use_tracers+x} ]; then
  use_tracers=y
fi

# Compile ONLY used modules to VASTLY reduce the number of modules built
# and the build time.
#
# To keep track of which modules are needed for your specific system/hardware,
# give module_db script a try: https://aur.archlinux.org/packages/modprobed-db
# This PKGBUILD read the database kept if it exists
#
# More at this wiki page ---> https://wiki.archlinux.org/index.php/Modprobed-db
if [ -z ${_localmodcfg} ]; then
  _localmodcfg=n
fi

# Tweak kernel options prior to a build via nconfig
_makenconfig=

Personally I'm running now xanmod kernel compiled with this:

env use_numa=n use_tracers=n makepkg -s

Also, you can now put a file in your local repo to build this package with a custom config. You have to call this file myconfig.

Reference:

  # Put the file "myconfig" at the package folder (this will take preference) or "${XDG_CONFIG_HOME}/linux-xanmod/myconfig"
  # If we detect partial file with scripts/config commands, we execute as a script
  # If not, it's a full config, will be replaced

@cartesius same for me. Something changed in pacman or libarchive, xz is not extracted anymore...

A quick workaround is uncompressing patch with xz and copy to src/ directory, or use "xz -d" inside prepare() (also we should add xz as makedepend)...

Getting this 31/03/2021 23:44 CET:

$ env _microarchitecture=99 use_numa=n use_tracers=n use_pds=n _localmodcfg=y makepkg -sc
...
==> Extracting sources...
  -> Extracting linux-5.10.tar.xz with bsdtar
==> Starting prepare()...
patch: **** Can't open patch file ../patch-5.10.27-xanmod1 : No such file or directory
==> ERROR: A failure occurred in prepare().
    Aborting...

@cartesius thanks. Updated

Hi, isn't the pinned comment about compiling wrong? (edited on 2019-01-12 00:50 by figue) 22 is not native architecture, 99 is. Couple of days ago the pinned comment about building kernel was right (I hope).

@cartesius you can ignore this warning.

Please, is this the thing to ignore, right? ==> WARNING: Package contains reference to $srcdir usr/lib/modules/5.10.17-xanmod1-1-lts/build/tools/objtool/objtool

Updated to 5.10.

There is a new package in branch 5.4:

https://aur.archlinux.org/packages/linux-xanmod-lts54/

@figue Cool, thank you.

@cartesius probably Xanmod project will follow upstream, so soon I'll update this package to 5.10.

Hello, because 5.10 is new LTS already e.g. in linux-lts when do you expect to have XanMod kernel line matching the new 5.10 LTS line? Is there already?