Package Details: mesa-git 19.3.0_devel.117035.690d359b6f4-1

Git Clone URL: (read-only)
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
Provides: libva-mesa-driver=19.3.0_devel.117035.690d359b6f4-1, mesa=19.3.0_devel.117035.690d359b6f4-1, mesa-vdpau=19.3.0_devel.117035.690d359b6f4-1, opencl-, opencl-driver, opengl-driver, vulkan-driver, vulkan-intel=19.3.0_devel.117035.690d359b6f4-1, vulkan-mesa-layer=19.3.0_devel.117035.690d359b6f4-1, vulkan-radeon=19.3.0_devel.117035.690d359b6f4-1
Submitter: Krejzi
Maintainer: Lone_Wolf
Last Packager: Lone_Wolf
Votes: 158
Popularity: 0.37
First Submitted: 2014-06-19 21:33
Last Updated: 2019-10-29 09:56

Required by (930)

Sources (2)

Pinned Comments

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.

Lone_Wolf commented on 2019-06-04 15:15

AUR Helpers are NOT supported

I built and test with makepkg. Building with Devtools and Clean Chroot Manager should work fine also (I test them occasionally).

This package and lib32-mesa-git use a custom method to dynamically determine which llvm version is to be used. Several AUR helpers (atleast pamac and yay) have problems with that method.

Incase you try to build mesa-git with one of those AUR helpers


run makepkg --printsrcinfo > .SRCINFO after downloading and BEFORE building.

That should help pamac and yay to handle my custom method.

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 »

yurikoles commented on 2019-06-29 21:10

What benefit will makepkg & devtools users get if I unset the var before running printsrcinfo ?

I know that this is AUR helper again, but for example in yay there is --devel option which checks for new commits in git repo and updates package only if remote was updated. I also do understand that it seems to be irrelevant for llvm/mesa which land new commits frequently. But running single command that updates all packages automgically is better than to do all this cd <some-path> && git fetch -p && git reset --hard origin/master && makepkg -si for all packages manually. Because simple git pull will just fail in case of new version in AUR and fact that pkgver is dynamically updated in PKGBUILD file. So those AUR helpers really help.

In case of [lib32-]mesa-git this requires manual workaround to be involved like explicitly adding these packages to IgnorePkg, because in case of update yay automatically pulls llvm-git, which is stated in mesa-git .SRCINFO.

You may ask why not to use llvm-gitfrom [mesa-git] repo? In this case mesa-git is also pulled from this repo instead of AUR and only option is to first install some llvm-git binary package then disable this repo. And now we are in a loop, because we also need to IgnorePkg llvm-git which will be pulled from AUR in this case. [llvm-svn] repo is not an option, it's very outdated. So having mesa-git built from source requires also to rebuilding llvm-git all the time, because there is no [llvm-git] repo available with fresh version of llvm-git. And keeping old llvm-git build installed is worse than having stable version installed from official repo, because you lose not only stability, but also fresh new features in same time, because this build will be unstable and old in same time.

Lone_Wolf commented on 2019-06-29 19:40

by Yurikoles @Lone_Wolf Why don't you just generate it with MESA_WHICH_LLVM='' makepkg --printsrcinfo > .SRCINFO before uploading to AUR?

I could do that, but it looks to me as that will only benefit aur helpers users.

The way MESA_WHICH_LLVM works now is not a solution i'm proud of, but it does work fine with makepkg & devtools.

What benefit will makepkg & devtools users get if I unset the var before running printsrcinfo ?

Lone_Wolf commented on 2019-06-29 19:35

Thanks, bpierre and Haxk20

src/gallium/targets/opencl/ file in mesa master has changed since the mesa MR was created, so I have created my own version.

Haxk20 commented on 2019-06-29 16:08


bpierre commented on 2019-06-29 15:13

Looks like it's missing a dependency on one of clang's libraries:

 PKGBUILD                   |  4 ++++
 gallium_opencl_clang.patch | 15 +++++++++++++++
 2 files changed, 19 insertions(+)

diff --git c/PKGBUILD i/PKGBUILD
index 3409ac1..bc44468 100644
@@ -25,10 +25,13 @@ conflicts=('mesa' 'opencl-mesa' 'vulkan-intel' 'vulkan-radeon' 'libva-mesa-drive
+        'gallium_opencl_clang.patch'
+         '5b5222192408b32f642f67f64a997719'
+            'ba54c5d0a11e23aa18236e48ea6a0954e2f10066757310ab53595b78818c779d4f3df2b8cd1a34d2b2caeedb1682c6ec3a70ccce6e9bcabfbe11da2101b225ac'

 # NINJAFLAGS is an env var used to pass commandline options to ninja
@@ -88,6 +91,7 @@ prepare() {
     if [  -d _build ]; then
         rm -rf _build
+    (cd mesa && patch -p1 < "$srcdir/gallium_opencl_clang.patch")

 build () {
diff --git c/gallium_opencl_clang.patch i/gallium_opencl_clang.patch
new file mode 100644
index 0000000..e98bb74
--- /dev/null
+++ i/gallium_opencl_clang.patch
@@ -0,0 +1,15 @@
+ src/gallium/targets/opencl/ | 1 +
+ 1 file changed, 1 insertion(+)
+diff --git i/src/gallium/targets/opencl/ w/src/gallium/targets/opencl/
+index 317ad8dab4a..650a2054cfb 100644
+--- i/src/gallium/targets/opencl/
++++ w/src/gallium/targets/opencl/
+@@ -51,6 +51,7 @@ libopencl = shared_library(
+     cpp.find_library('clangSema', dirs : llvm_libdir),
+     cpp.find_library('clangAnalysis', dirs : llvm_libdir),
+     cpp.find_library('clangAST', dirs : llvm_libdir),
++    cpp.find_library('clangASTMatchers', dirs : llvm_libdir),
+     cpp.find_library('clangEdit', dirs : llvm_libdir),
+     cpp.find_library('clangLex', dirs : llvm_libdir),
+     cpp.find_library('clangBasic', dirs : llvm_libdir),

Haxk20 commented on 2019-06-29 14:48

MESA fails to build with the clang from mesa-git repo. Here is the full build log:

yurikoles commented on 2019-06-20 11:43


Why don't you just generate it with

MESA_WHICH_LLVM='' makepkg --printsrcinfo > .SRCINFO

before uploading to AUR?

Terence commented on 2019-06-10 19:06

Thanks Lone_Wolf for pointing me to the right direction. I successfully created my own patch based on the MR, modified the libglvnd PKGBUILD to apply it and the missing files are now provided.

I opened a feature request on the tracker: Feel free to upvote it if you also have this problem and try the attached PKGBUILD and patch.

Lone_Wolf commented on 2019-06-10 10:58

Mesa 19.1 will include that commit, so both mesa-git and stock mesa would have to revert the commit.

Solving this in libglvnd is a much better solution .

The glvnd bug has a proposed patch (from april 28 ), try applying that to the glvnd package using abs/asp . Anyone willing to start a patched glvnd package should/could ask help on forum or arch-general, aur-general mailing lists.

Terence commented on 2019-06-09 02:10

Since, mesa doesn't provide and glesv2.pc anymore resulting in building problems: Can the commit be reverted until libglvnd behaves correctly?