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 8 9 10 ... Next › Last »

Lone_Wolf commented on 2020-07-02 14:45

Both archlinux and mesa bugtrackers don't show LTO related problems with mesa afaik.

Re-enabled LTO.

Lone_Wolf commented on 2020-06-23 11:29

Yup, removed the relevant commands.

phush0 commented on 2020-06-23 07:53

ninja: Entering directory `_build'
ninja: error: unknown target 'xmlpool-pot'

It will not build

Edit: It seem changed translation facilities in patch 2ef983dca61b549a9242afd9008200b231a26e90

Lone_Wolf commented on 2020-06-02 14:17

Yes, this is a side effect of my request to increase the minimum meson version .

I'll look into updating the meson options, hopefully this week.

Edit : enabling LTO did increase built time considerably. While it decreased the size of the binaries, I'm not sure of performance benefits. For now i'm keeping it disabled.

fisch02 commented on 2020-06-02 13:28

Since, "true" and "false" were deprecated in favor of "enabled" and "disable" for some options. This throws a warning of the form "WARNING: (Optionname) option "true" deprecated, please use "enabled" instead." during build. The build() function of the PKGBUILDs for mesa-git and lib32-mesa-git should therefore be edited correspondingly. EDIT: Btw. with issue #2977 being closed, lto could now be enabled again

ph34rb0t commented on 2020-05-18 18:48

Yes, that bug report set me onto the right track regarding lto.

Thanks for the PKGBUILD fix!

Lone_Wolf commented on 2020-05-17 22:48

Yep, mesa , lto and gcc 10.1 don't seem to work together.

see and

Disabled lto in this package, will do lib32-mesa-git soon.

ph34rb0t commented on 2020-05-16 15:59

I had to set "-D b_lto=true" to "false" in the PKGBUILD to prevent Plasmashell and any OpenGL app (e.g. glxinfo, glxgears) from crashing. (Built against the standard llvm and llvm-libs packages.)

(Edited original post with solution and made it more concise.)

gort818 commented on 2020-05-15 14:29

Yes it is.

Lone_Wolf commented on 2020-05-15 10:07

Is the bugreport you filed ?