Package Details: mesa-git 21.3.0_devel.146044.77e5f149ebb-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: 165
Popularity: 0.41
First Submitted: 2014-06-19 21:33
Last Updated: 2021-10-13 22:50

Dependencies (34)

Required by (1000)

Sources (2)

Pinned Comments

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

  • choosing which llvm variant to build against

WARNING : aur helpers don't support this method at all. They check .SRCINFO and that is set to build against repo llvm when it is uploaded.

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.

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

1 2 3 4 5 6 ... Next › Last »

Lone_Wolf commented on 2021-10-20 08:59

libffi has been updated and this requires a rebuild of all llvm trunk variants.

After that rebuild has finished you will need to rebuild this pacakge also .


I don't know if repo llvm will also need a rebuild. can help to determine that.

rjahanbakhshi commented on 2021-10-13 22:50

Patch removed since it's already applied upstream.

Lone_Wolf commented on 2021-10-13 20:28

confirmed, my MR for it has been accepted into main. see

For now just edit the PKGBUILD and comment out the 1 line in prepare() that starts with patch .

fl2021 commented on 2021-10-13 19:19

I get a build error with that patch:

==> Starting prepare()... patching file src/gallium/frontends/clover/llvm/codegen/native.cpp Reversed (or previously applied) patch detected! Skipping patch. 1 out of 1 hunk ignored -- saving rejects to file src/gallium/frontends/clover/llvm/codegen/native.cpp.rej patching file src/gallium/frontends/clover/llvm/compat.hpp Hunk #1 succeeded at 62 with fuzz 1 (offset 6 lines). ==> ERROR: A failure occurred in prepare(). Aborting...

Edit: It looks like your commit got merged, so maybe that's why the pkgbuild is failing trying to apply it again.

rjahanbakhshi commented on 2021-10-11 09:25

Patch added to solve a build failure, see

rjahanbakhshi commented on 2021-10-11 09:14


Thanks for the update. I can update the PKGBUILD and apply the patch. I'm testing it.

Lone_Wolf commented on 2021-10-11 08:37

Those building against llvm 14 will get a build failure, See .

mesa-minimal-git already has the patch, I'll try to add it to this package soon.

Lone_Wolf commented on 2021-09-13 12:37

MR 12715 has been added to main, but this only solves part of the issue.

Patch needs to be adjusted (already done for mesa-minimal-git) . Will try to do mesa-git /lib32-mesa-git later today.

Lone_Wolf commented on 2021-09-10 14:59

Patch applied.

matt_ryanb, I don't see how that can happen.

Even if it did happen, build should be aborted immediately as mesa-git conflicts with mesa and lib32-mesa-git has a hard dependency on mesa-git (and conflicts lib32-mesa-git) .

I'd have to see build logs to investigate what goes wrong.

matt_ryanb commented on 2021-09-10 10:31

Nice, cheers. I've also noticed when building (lib32-)mesa-git that makepkg pulls in the latest repo mesa as a runtime dependency, which seems...counter-intuitive. Any explanation as to why this happens?