Buildbot for Archlinux based repos with different x86-64 feature levels, -O3 and LTO.

• Quick Start
• FAQ
• Matrix
• Donations
• License and Legal

Check which feature levels your CPU supports with

/lib/ld-linux-x86-64.so.2 --help

Example output snippet for a system supporting up to x86-64-v3:

Subdirectories of glibc-hwcaps directories, in priority order:
  x86-64-v4
  x86-64-v3 (supported, searched)
  x86-64-v2 (supported, searched)

Install alhp-keyring and alhp-mirrorlist from the AUR.

Example with yay:

yay -S alhp-keyring alhp-mirrorlist

alhp-keyring provides the current signing keys used by ALHP, alhp-mirrorlist a selection of mirrors.

Edit /etc/pacman.d/alhp-mirrorlist and comment in/out the mirrors you want to enable/disable. By default, a CDN mirror provided by ALHP is selected.

Add the ALHP repos to your /etc/pacman.conf. Make sure the appropriate ALHP repository is above the Archlinux repo.

Example for x86-64-v3:

[core-x86-64-v3]
Include = /etc/pacman.d/alhp-mirrorlist

[core]
Include = /etc/pacman.d/mirrorlist

[extra-x86-64-v3]
Include = /etc/pacman.d/alhp-mirrorlist

[extra]
Include = /etc/pacman.d/mirrorlist

# if you need [multilib] support
[multilib-x86-64-v3]
Include = /etc/pacman.d/alhp-mirrorlist

[multilib]
Include = /etc/pacman.d/mirrorlist

Replace x86-64-v3 with the x86-64 feature level you want to enable.

pacman -Suy

To disable ALHP, remove all x86-64-vX entries in /etc/pacman.conf and remove alhp-keyring and alhp-mirrorlist.

After that, you can update pacman's databases and downgrade all packages, like

pacman -Suuy

Enabled for all packages built after 04 Nov 2021 12:07:00 UTC. More details. LTO status is visible per package on the package status page.

KCFLAGS/KCPPFLAGS are used to build the kernel packages with our additional flags.

Due to our increase in pkgrel, building the kernel packages will break any directly linked modules such as nvidia (not nvidia-dkms) or virtualbox-host-modules-arch (not virtualbox-host-dkms). Their respective dkms-variant is not affected. This issue is being tracked in #68, a solution is being worked on.

You want to mirror ALHP? You are welcome to do so, see alhp-mirrorlist for how to become one.

Packages excluded from building (besides all any architecture packages) are being listed in issue #16. See also package status page (search for blacklisted).

Also relevant for: I can't find package X / Application X fails to start because it links to an old/newer lib

ALHP builds packages after they are released in the official Archlinux repos (excluding [*-testing]). This will cause packages to be delayed if the current batch contains many packages, or packages that take a while to build (e.g. chromium).

You can always check on the progress of the current build cycle on the package status page. Please refrain from opening issues caused by packages currently in queue/not yet build/not yet moved to the repo. Please keep in mind that large rebuilds such as openssl or python can take days to complete on our current build hardware.

ALHP provides a debuginfod instance under debuginfod.alhp.dev.

To use it, have debuginfod installed on your system and add it to your DEBUGINFOD_URLS with:

echo "https://debuginfod.alhp.dev" > /etc/debuginfod/alhp.urls

If you want to switch between levels, e.g. from x86-64-v3 to x86-64-v4, you need to revert to official packages first, and then enable your desired repos again.

1. Comment out or remove the ALHP repo entries in /etc/pacman.conf.
2. Downgrade packages with pacman -Suuy.
3. Clear pacman's package cache with pacman -Scc.
4. Uncomment/add your desired repos to /etc/pacman.conf and update with pacman -Suy.

For any non-issue questions, or if you just want to chat, ALHP has a Matrix room here (#alhp@ofsg.eu). You can also find me (@idlegandalf) in #archlinux:archlinux.org.

I appreciate any money you want to throw my way, but donations are strictly optional. Donations are primarily used to pay for server costs. Also consider donating to the Archlinux Team, without their work ALHP would not be possible.

This project and all of its source code is released under the terms of the GNU General Public License, version 2 or any later version. See LICENSE for details.