Arch Linux User Repository

To those with the directx errors : archlinux directx-headers pacakgae is 2 releases behind upstream. Try building against aur directx-headers-git .

I don't remember what d3d12 does, but offical mesa also supports it.

@ZephyrCheez : thanks, that option lead to meson subprojects and mesa sourcetree does appear to include the data needed to use them. Adding nouveau vulkan looks doable now, no idea when there will be time to implement it.

@Beiruty, those have the same cause as the other recent build failures : changes in intel drivers.

The build issues caused by changes in intel drivers are now solved for MESA_WHICH_LLVM 1, 3 and 4 (llvm-minimal-git , llvm from lordheavy unofficial repo and offical repo llvm )

MESA_WHICH_LLVM 2 (aur llvm-git) build is still broken, but I MAY have a solution for that without having to create new packages.

The good news is that once all 4 variants built again, only minor changes should be needed to add opencl clover & opencl rusticl support.

(A lot of the work required to built the intel drivers is also useful for clover & rusticl)

Mesa and llvm are closely tied together. Everytime the llvm mesa is built against changes/updates , mesa needs to be rebuilt.

I expect anyone building mesa-git against one of the llvm trunk variants to be able to do that themselves, but atleast some of the people that built against repo llvm don't understand how to deal with such a rebuild.

The rest of this post is meant for those people.

• Verify if latest PKGBUILD requirements match llvm repo versions.
• If they don't , post to alert the maintainer of this.
• DELAY the update of llvm/clang suite and their lib32- counterparts
• Once the PKGBUILD does match, download it.

Option A - best one

• run pacman -Syu to ensure your system is in sync with your mirrror server
• build mesa-git in a clean chroot

see https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_clean_chroot for the official way or https://aur.archlinux.org/packages/clean-chroot-manager for an alternative method.

• install the newly built mesa-git
• run pacman -Syu
• ready

Option B - 2nd best

• revert to repo mesa
• pacman -Syu
• build mesa-git
• switch from mesa to mesa-git
• ready

• choosing which llvm variant to build against

WARNING : aur helpers don't support this method at all. They check .SRCINFO and that doesn't include this variable so it will use the default which is hardcoded to build against repo llvm.

Why would I want to use llvm development versions ?

For full functionality and latest features mesa trunk master needs to be build against llvm trunk master.
If you build against stable llvm things MAY work, but you're likely to lack some features and face stability issues.

Mesa-git uses a custom environment variable MESA_WHICH_LLVM for flexibility.
It has 4 values.
1 : aur llvm-minimal-git
2 : aur llvm-git
3: llvm-git from LordHeavy' unofficial repo
4: llvm from extra repo

I use value 1 95% of the time and set this in ~/.bash_rc .
If MESA_WHICH_LLVM is unset or empty, the default value of 4 (extra llvm) is used.

• main difference with stable repo package

[extra]mesa is a split package, but aur mesa-git isn't.
Basically with aur mesa-git you get everything in one package, while [extra]/mesa allows you to leave out some parts if you don't want/need them.
Having a single package reduces maintenance and makes switching from stable to mesa-git rather easy, though reverting back to stable can be tricky.

• meson settings

Those who compare PKGBUILDs will notice I don't use arch-meson, but meson setup.
I disagree with some of the settings made by arch-meson (especially the buildtype and enabling LTO by default) and feel using meson setup is cleaner.

• how to update

run pacman Syu update non-repo packages for llvm if you use them

build mesa-git, log out , update mesa-git and restart X .

run glxinfo -B to verify basic OpenGL functionality

build lib32-mesa-git

run glxinfo32 -B to verify basic OpenGL functionality for multilib programs

The new pkgver() breaks when not using main (as documented).

It does indeed fail with branch staging/23.2 but I can't pinpoint the cause as it seems to fail upon entering pkgver .

Where can that documentation be found ?

As for adding an extra option for llvm : can be considered when/if someone creates an aur package for it.

From my POV the new pkgver() is a PITA. I have little to no interest in tracking the main git branch. I do however, like to track the staging/2x.y branch or the tagged rcx versions. The new pkgver() breaks when not using main (as documented). It would be VERY nice if there was a commmented out section in pkgver() which we could enable to let tagged or other branches build. I tracked mesa 23.1-rcx version with no noticed llvm issues. That being said, I have a manually built copy of llvm in $HOME/local/llvmxx (see aur zig-git)- it would be nice if there was a fifth option to easily select this llvm.

The pkgver() function used is based on the no tags version for git packages from the VCS guidelines gitpage.

Many users asked for something to easily compare this version with that of the stable version in repos. The only method to get this value in a reliable & reproducible way is to retrieve it directly from the VERSION file .

The patchver part is taken from the official archlinux PKGBUILD for linux.

Keep in mind that the archlinux dev Lord Heavy uses the same pkgver() (except for the patchver part) in his unofficial mesa-git repository , see https://gitlab.com/lordheavy/mesa-git/-/blob/master/mesa-git/PKGBUILD .

The AUR mesa-minimal-git packages and several other mesa trunk packages also use such a pkgver() .

Changing the pkgver() only for mesa-git and lib32-mesa-git would be confusing .

Please implement a proper pkgver() function as per Arch guidelines.

Thanks for the input , HurricanePootis . If mesa-git only needed to build against repo llvm/clang your patch would work. Unfortunately that's not the case.

Mesa-git package supports building against 4 llvm variants (three of which are llvm trunk versions). Any options used need to work with all of them. I see four changes in your patch and will discuss them below.

• adding intel-nullhw: while it seems to be exlusively used for debugging on intel hardware, it is an official vulkan extension and could be added.

• enabling intel-clc : supports raytracing with vulkan on some intel hardware. I am not aware of it being enabled in any aur mesa trunk package so it will need to be tested. If you (or others) want to help try building mesa-git with that option enabled against llvm-minimal-git or llvm-git (once those are confirmed to work, building against lordheavy's llvm trunk packages would also help).

• opencl-mesa in repos provides 2 things : clover and rusticl .

• clover (aka gallium-opencl) build has been broken with llvm trunk (17+) since februari and continues to fail. The bug ticket https://gitlab.freedesktop.org/mesa/mesa/-/issues/8591 hasn't seen recent activity. Until it is solved mesa-git can't re-enable it.

• rusticl

quoted from https://docs.mesa3d.org/rusticl.html SPIRV-LLVM-Translator for a libLLVMSPIRVLib.so matching your version of LLVM, i.e. if you’re using LLVM 15 (libLLVM.so.15), then you need a libLLVMSPIRVLib.so.15.1

extra/spirv-llvm-translator is build against repo llvm and doesn't work with llvm trunk. All llvm trunk varaints need their own version of spirv-llvm-tranalator AND libclc build against their specific llvm variant.

currently those packages don't exist for llvm-git. Someone needs to create and maintain them. Once that has been done rusticl will work with all 4 llvm variants supported by this package and can be added.

If anyone wants to give it a try, look at my aur spirv-llvm-translator-minimal-git & libclc-minimal-git packages to get started.

Hello, this is a comment with a patch that will make mesa-git more in-line with mesa. This patch adds Rusticl, intel-clc, renables opencl-mesa, and adds the required makedeps and depends for rusticl and intel-clc. I have also left a comment on lib32-mesa-git that has a singular patch that will make it more in-line with lib32-mesa.

diff --git a/PKGBUILD b/PKGBUILD
index a68b5a5..02c732f 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -12,14 +12,15 @@

 pkgname=mesa-git
 pkgdesc="an open-source implementation of the OpenGL specification, git version"
-pkgver=23.2.0_devel.172019.732db2b60cd.d41d8cd98f00b204e9800998ecf8427e
+pkgver=23.2.0_devel.173428.86785130d18.d41d8cd98f00b204e9800998ecf8427e
 pkgrel=1
 arch=('x86_64')
 makedepends=('git' 'python-mako' 'xorgproto'
               'libxml2' 'libx11'  'libvdpau' 'libva' 'elfutils' 'libxrandr'
-              'wayland-protocols' 'meson' 'ninja' 'glslang' 'directx-headers' 'libclc')
+              'wayland-protocols' 'meson' 'ninja' 'glslang' 'directx-headers' 'libclc' 'rust' 'rust-bindgen' 'spirv-tools'
+              'python-ply' 'spirv-llvm-translator')
 depends=('libdrm' 'libxxf86vm' 'libxdamage' 'libxshmfence' 'libelf'
-         'libomxil-bellagio' 'libunwind' 'libglvnd' 'wayland' 'lm_sensors' 'libclc' 'vulkan-icd-loader' 'zstd' 'expat')
+         'libomxil-bellagio' 'libunwind' 'libglvnd' 'wayland' 'lm_sensors' 'libclc' 'vulkan-icd-loader' 'zstd' 'expat' 'spirv-llvm-translator')
 optdepends=('opengl-man-pages: for the OpenGL API man pages')
 provides=('mesa' 'opencl-mesa' 'vulkan-intel' 'vulkan-radeon' 'vulkan-mesa-layer' 'libva-mesa-driver' 'mesa-vdpau' 'vulkan-swrast' 'vulkan-driver' 'mesa-libgl' 'opengl-driver' 'opencl-driver')
 conflicts=('mesa' 'opencl-mesa' 'vulkan-intel' 'vulkan-radeon' 'vulkan-mesa-layer' 'libva-mesa-driver' 'mesa-vdpau' 'vulkan-swrast' 'mesa-libgl')
@@ -119,15 +120,17 @@ build () {
        -D b_ndebug=true \
        -D b_lto=false \
        -D platforms=x11,wayland \
+       -D rust_std=2021 \
        -D gallium-drivers=r300,r600,radeonsi,nouveau,virgl,svga,swrast,i915,iris,crocus,zink,d3d12 \
        -D vulkan-drivers=amd,intel,swrast,virtio,intel_hasvk \
-       -D vulkan-layers=device-select,overlay \
+       -D vulkan-layers=device-select,overlay,intel-nullhw \
        -D dri3=enabled \
        -D egl=enabled \
        -D gallium-extra-hud=true \
        -D gallium-nine=true \
        -D gallium-omx=bellagio \
-       -D gallium-opencl=disabled \
+       -D gallium-opencl=icd \
+       -D gallium-rusticl=true \
        -D gallium-va=enabled \
        -D gallium-vdpau=enabled \
        -D gallium-xa=enabled \
@@ -136,6 +139,7 @@ build () {
        -D gles2=enabled \
        -D glvnd=true \
        -D glx=dri \
+       -D intel-clc=enabled \
        -D libunwind=enabled \
        -D llvm=enabled \
        -D lmsensors=enabled \

@kanadeaur : that output indicates you're not using this package but Lordheavy's mesa-git repository, see https://wiki.archlinux.org/title/Unofficial_user_repositories#mesa-git .

We can't help with that.

I have a problem with installing mesa-git:

[kanade@kanade-pc ~]$ sudo pacman -Syu mesa-git :: Synchronizing package databases... core is up to date extra is up to date multilib is up to date mesa-git is up to date :: Starting full system upgrade... resolving dependencies... looking for conflicting packages... :: mesa-git and mesa are in conflict. Remove mesa? [y/N] y

Packages (3) llvm-libs-git-17.0.0_r465461.eaaacc3c651e-1 mesa-23.1.3-1 [removal] mesa-git-1:23.2.0_devel.173277.0d9f474381b-1

Total Download Size: 16,62 MiB Total Installed Size: 257,84 MiB Net Upgrade Size: 169,20 MiB

:: Proceed with installation? [Y/n] Y :: Retrieving packages... llvm-libs-git-17.0.0_r465461.eaaacc3c651e-1-x86_64 is up to date Total (1/2) 16,6 MiB 177 MiB/s 00:00 [###############################################] 100% error: failed retrieving file 'llvm-libs-git-17.0.0_r465461.eaaacc3c651e-1-x86_64.pkg.tar.zst.sig' from pkgbuild.com : The requested URL returned error: 404 warning: failed to retrieve some files error: failed to commit transaction (failed to retrieve some files) Errors occurred, no packages were upgraded.

This package builds mesa trunk. mesa 3.1 was branched off from trunk on april 10 . That means trunk is now hundreds of commits ahead of mesa stable.

Do you have proof that your error is also present in (recent) mesa trunk builds ?

Today's update broke WebGL in browser (for example - maps.google.com).

Downgrading mesa to mesa-23.0.3-1 solved the issue for me: pamac install downgrade && downgrade mesa