Package Details: mesa-git 21.1.0_devel.135859.a1e9a5d6534-1

Git Clone URL: (read-only, click to copy)
Package Base: mesa-git
Description: an open-source implementation of the OpenGL specification, git version
Upstream URL:
Keywords: mesa X11
Licenses: custom
Conflicts: libva-mesa-driver, mesa, mesa-vdpau, opencl-mesa, vulkan-intel, vulkan-mesa-layer, vulkan-radeon, vulkan-swrast
Provides: libva-mesa-driver, mesa, mesa-vdpau, opencl-driver, opencl-mesa, opengl-driver, vulkan-driver, vulkan-intel, vulkan-mesa-layer, vulkan-radeon, vulkan-swrast
Submitter: Krejzi
Maintainer: Lone_Wolf (rjahanbakhshi)
Last Packager: rjahanbakhshi
Votes: 163
Popularity: 1.27
First Submitted: 2014-06-19 21:33
Last Updated: 2021-03-03 09:02

Dependencies (34)

Required by (1000)

Sources (3)

Pinned Comments

Lone_Wolf commented on 2021-01-03 15:38

I am using another package now and am looking for a new maintainer.

Lone_Wolf commented on 2020-04-23 12:26

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 me 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 for the official way or 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

Lone_Wolf commented on 2019-07-09 13:43

  • 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.

AUR helpers like yay and pamac can't deal with such a dynamic choice. People who use those will have to accept the default of building mesa-git against stock repo packages.

Lone_Wolf commented on 2018-01-30 14:06

  • issues
Simple issues can be dealth with through aur comments, but sometimes discussion is needed.
Use for that.
  • 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 , restart X .

run glxinfo to verify basic OpenGL functionality

build lib32-mesa-git

run glxinfo32 to verify basic OpenGL functionality for multilib programs

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 ... Next › Last »

zilot commented on 2021-01-17 14:59

Some people had the same issue I had when trying to update their system

error: failed to prepare transaction (could not satisfy dependencies)
:: installing lib32-llvm-libs (11.0.1-1) breaks dependency 'lib32-llvm-libs=11.0.0' required by lib32-mesa-git
:: installing llvm-libs (11.0.1-1) breaks dependency 'llvm-libs=11.0.0' required by mesa-git

To update your system anyway, you need to ignore those two package with the --ignore option :

sudo pacman -Syu --ignore=lib32-llvm-libs,llvm-libs

This ignore them temporary. You need to modify your .conf file to make it permanent.

rjahanbakhshi commented on 2021-01-14 11:28


You can work around this issue by installing official extra/mesa which consequently removes mesa-git, then update using pacman, and reinstall mesa-git after.

sudo pacman -S mesa
sudo pacman -Syu
makepkg -sri

You could also use the clean chroot method. Please see the pinned comment above for the details. Here's the brief:

mkdir ~/chroot
mkarchroot $CHROOT/root base-devel
arch-nspawn $CHROOT/root pacman -Syu
makechrootpkg -c -r $CHROOT

Find the newly created mesa-git package by

ls -t *.zst | head -n1

Install the created package and update the system

sudo pacman -U mesa-git-xxx.pkg.tar.zst
sudo pacman -Syu

You can remove the created chroot directory to save the space if you want

sudo rm -rf $CHROOT

zangoku commented on 2021-01-13 18:51

I am unable to update it I get when updating llvm-libs:

error: failed to prepare transaction (could not satisfy dependencies)
:: installing lib32-llvm-libs (11.0.1-1) breaks dependency 'lib32-llvm-libs=11.0.0' required by lib32-mesa-git
:: installing llvm-libs (11.0.1-1) breaks dependency 'llvm-libs=11.0.0' required by mesa-git

I get this when updating mesa-git:

==> Missing dependencies:
  -> llvm-libs=11.0.1
==> Checking buildtime dependencies...
==> ERROR: Could not resolve all dependencies.
error making: mesa-git

HazardousBit commented on 2021-01-11 19:51

@le_tucan i just logged in to comment the same thing. Thanks for reporting

le_tucan commented on 2021-01-11 14:18

llvm got an update, so the dependencies are outdated, line 74 and 75 in PKGBUILD need to be ">=11.0.0"

Lone_Wolf commented on 2021-01-03 15:38

I am using another package now and am looking for a new maintainer.

Lone_Wolf commented on 2021-01-03 15:37

That's an adjustment for building with devtools, correcting now.

elovin commented on 2021-01-03 15:28

In the last commit "57e4140fd5bb" you added the line:


above the if statement:

if [[ ! $MESA_WHICH_LLVM ]] ; then MESA_WHICH_LLVM=4 fi

now the script always uses option 1 for MESA_WHICH_LLVM (minimal llvm)

Sinistar commented on 2020-12-21 22:35

VK_ICD_FILENAMES as a launch option has always worked for me in Steam. Now you got me wondering, I am going to recompile mesa with the swrast option and see what happen here.


Tested with amdvlk, vulkan-radeon, vulkan-mesa, and vulkan-intel. Without using VK_ICD_FILENAMES, Steam used amdvlk for the five games I tested. Without amdvlk, Steame use vulkan-radeon on every game. I don't see how swrast is causing a problem, unless it a dx12 proton issue. all games I tested were dx11.

Using VK_ICD_FILENAMES worked on every game also.

Lone_Wolf commented on 2020-12-21 14:12

A script like that will be very compilcated to get right, as there are atleast 7 possible vulkan drivers that theoretically can all be present at same time. vulkan-intel, nvidia-utils , vulkan-radeon, amdvlk, vulkan-amdgpu-pro and lavapipe (vulkan-mesa) .

I did some searching to get clear what the real problem is .

vulkaninfo from my own system

Layers: count = 2
VK_LAYER_MESA_device_select (Linux device selection layer) Vulkan version 1.1.73, layer version 1:
        Layer Extensions: count = 0
        Devices: count = 2
                GPU id = 0 (AMD RADV POLARIS10 (ACO))
                Layer-Device Extensions: count = 0

                GPU id = 1 (llvmpipe (LLVM 12.0.0, 256 bits))
                Layer-Device Extensions: count = 0

So lavapipe does support VK_LAYER_MESA_device_select .

I found several bugreports that appear relevant [1][2].

quoting from [2]

Using a custom per-game driver (like with VK_ICD_FILENAMES or LIBGL_DRIVERS_PATH) doesn't work

This suggests that the problem is not with lavapipe, but in steam / proton having trouble if there's more then one vulkan driver present.

That means disabling lavapipe won't solve the issue since there will still be 2 vulkan drivers present : RADV (vulkan-radeon) & ANV (vulkan-intel) .

Even splitting of the 3 vulkan drivers to their own packages will still allow installing 2 or more unless I have them conflict .

Telling people to remove drivers they don't use from /usr/share/vulkan/icd.d/ seems an easier and cleaner workaround .