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

Mesa commit b52e25d3 breaks intel iris & anv build UNLESS OpenCL support is present.

Incase you don't need those drivers, a temporary workaround is to disable them.

lib32-mesa-git & lib32-mesa-minimal-git are also affected.

mesa-minimal-git is NOT affected.

@MrNessuno :

This is not distro specific as sofar users of Archlinux, Endeavour OS, Manjaro AND fedora have reported it.

About a year ago mesa-minimal-git had an lto related issue with text scrolling.
My testing results then suggest the issue was caused by to many gallium drivers being built or maybe a incompatibility between some gallium drivers.

Try an LTO enabled build with only the gallium driver(s) your system needs . (examples: radeonsi for amd-only, iris + radeonsi for a recent intel + amd system)

You may also have to reduce the vulkan targets as they typically need a specific gallium driver.

If that build doesn't have the issues, more testing can narrow down the cause further.

@Lone_Wolf Do you know on Manjaro what is breaking it with LTO enabled? Seems to be a better thing to have. How we can fix it?

@Grabbend:

First, VCS packages in general and this package especially are a bad match for aur helpers and unattended building.

Second, xwayland gets it's settings from the wayland compositor that calls it. In order to troubleshoot the issue people with knowledge about wlroot , sway, xwayland and mesa-git will need to cooperate. stackoverflow might have those people and is distro neutral. You can try asking there.

Onto unattended building mesa-git. There will be build / update failures when using mesa-git . One guaranteed cause is llvm changing sonames which happens everytime you want to update to a new major llvm version (sometimes this also happens with minor versions).

Your workaround of force removing mesa means your system will not be in a consistent usable state until mesa-git gets installed later in the process. If you face a power failure, a build failure or an install failure during that time your system will likely lose all GUI functionality.

Fortunately there's a better method, some analysis of what happens first

• mesa needs libglvnd present at buildtime in order to support glvnd at runtime
• libglvnd has a hard dependency on mesa

• ANY package that provides mesa will satisfy the dep

• solution:

step 1 Ensure the previous mesa-git is available (incase you haven't got one yet, build manually one time)

step 2 prepare clean chroot building so the build environment will be isolated from your live system

step 3 instruct the chroot build to install the mesa-git from step 1

step 4 run the clean chroot build

step 5 if everything is succesfull, install the new mesa-git to the live system.

The method outlined above will work with archlinux devtools and any aur helper that implements clean chroot building properly.

Look at chrootctl on paru manpage to find the parameter you need to use in step 3.

Found a major problem:

There's a circular dependency loop in aur/mesa-git as seen here (truncated):

$ paru --query --info mesa
error: package 'mesa' was not found

$ paru --noconfirm --sync aur/mesa-git
:: Conflicts found:
    mesa-git: mesa (mesa-libgl)  mesa  mesa (mesa-libgl)  

libglvnd is slated as a dependency and it's responsible for pulling in: extra/mesa when building aur/mesa-git. This causes unattended build scripts to fail (since --noconfirm selects N):

:: mesa-git and mesa are in conflict. Remove mesa? [y/N] 

(The above can be confirmed with this when $ paru --noconfirm --sync aur/mesa-git fails):

$ paru --query --info mesa | grep 'Required'
Required By     : libglvnd

(Here's another way to confirm this command as long as mesa nor mesa-git aren't installed):

$ paru --sync libglvnd
resolving dependencies...
looking for conflicting packages...
warning: dependency cycle detected:
warning: mesa will be installed before its libglvnd dependency

Workaround:

$ paru --sync libglvnd
$ paru --remove --nodeps --nodeps mesa
$ paru --noconfirm --sync aur/mesa-git

Workaround 2:

$ paru --sync --noconfirm --needed --assume-installed mesa,opengl-driver --asdeps libglvnd
$ paru --sync --noconfirm --needed aur/mesa-git

Edit: I've also reported this here

https://gitlab.archlinux.org/archlinux/packaging/packages/libglvnd/-/issues/2

Has anyone figured why latest MESA (aur/mesa-git aur/lib32-mesa-git) is trying to use Zink for everything under XWayland? This prevents applications from starting like: steam-native, firefox, google-chrome & codium

I'm using RX 6800 XT & Sway (Git)

There's some users reporting this issue in various forums but there is no clear solution (I've even re-installed the entire system)

Error

DRI3 not available
failed to load driver: zink

WORKAROUND

For what it's worth I managed to fix this in CachyOS by:

1. Replacing aur/mesa-git with aur/amdonly-gaming-mesa-git (MESA TKG also worked).
2. Installed aur/xorgproto-git (depends on previous).
3. Installed aur/xorg-xwayland-git (depends on previous).
4. Installed aur/wlroots-git (it has to be built before building sway-git).
5. Installed aur/sway-git (that's my Window Manager, it needs xorg-xwayland-git due to recent changes in seat management).

No more issues! :)

# HW (deps)
$ paru --noconfirm --sync --needed --noprovides \
    --assume-installed mesa,opengl-driver,xorgproto \
    --asdeps libglvnd aur/xorgproto-git

# HW (amdgpu)
$ paru --noconfirm --sync --needed --noprovides \
    aur/amdonly-gaming-mesa-git \
    aur/amdonly-gaming-vulkan-radeon-git \
    aur/amdonly-gaming-vulkan-mesa-layers-git \
    aur/amdonly-gaming-libva-mesa-driver-git \
    aur/amdonly-gaming-mesa-vdpau-git

# WM (deps)
$ paru --noconfirm --sync --needed --noprovides aur/xorg-xwayland-git

# WM (runtime)
$ paru --noconfirm --sync --needed --noprovides aur/wlroots-git && \
  paru --noconfirm --sync --needed --noprovides aur/sway-git

Edit: Another tip is to always make sure your current LLVM version matches the LLVM version which MESA was built with (to avoid strange issues).

LTO stands for Link Time Opmization and is supposed to reduce binary sizes and improve performance.

https://en.wikipedia.org/wiki/Interprocedural_optimization

Many distros including fedora & archlinux enable it by default. The majority of programs benefit from it, those that don't (or show buildtime / runtime issues when built with LTO) need to disable it explicitly.

gcc & llvm on archlinux both disable LTO, mesa results with lto builds vary.

Can confirm also, now works on Manjaro also. Pardon my ignorance, but what is this "LTO" supposed to do anyway? Make compiling the package faster or actually make drivers performance faster?

Seems there are still issues with LTO so I disabled it again.

I can confirm, after disabling LTO everything works again.

If you are running arch and plasma and would like to edit the PKGBUILD, On line 124, change -D b_lto=true to -D b_lto=false

Here is the command: yay -S mesa-git --editmenu --editor kate