Package Details: mesa-git 23.3.0_devel.174362.a944a8eba93.d41d8cd-1

Git Clone URL: https://aur.archlinux.org/mesa-git.git (read-only, click to copy)
Package Base: mesa-git
Description: an open-source implementation of the OpenGL specification, git version
Upstream URL: https://www.mesa3d.org
Keywords: mesa wayland X11
Licenses: custom
Conflicts: libva-mesa-driver, mesa, mesa-libgl, mesa-vdpau, opencl-mesa, vulkan-intel, vulkan-mesa-layer, vulkan-radeon, vulkan-swrast
Provides: libva-mesa-driver, mesa, mesa-libgl, mesa-vdpau, opencl-driver, opencl-mesa, opengl-driver, vulkan-driver, vulkan-intel, vulkan-mesa-layer, vulkan-radeon, vulkan-swrast
Submitter: Krejzi
Maintainer: rjahanbakhshi (Lone_Wolf)
Last Packager: rjahanbakhshi
Votes: 173
Popularity: 0.66
First Submitted: 2014-06-19 21:33 (UTC)
Last Updated: 2023-07-19 10:35 (UTC)

Required by (1515)

Sources (2)

Pinned Comments

Lone_Wolf commented on 2020-04-23 12:26 (UTC) (edited on 2023-03-30 07:04 (UTC) by Lone_Wolf)

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

Lone_Wolf commented on 2019-07-09 13:43 (UTC) (edited on 2023-04-18 10:41 (UTC) by Lone_Wolf)

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

Lone_Wolf commented on 2018-01-30 14:06 (UTC) (edited on 2023-02-12 11:56 (UTC) by Lone_Wolf)

  • 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

Latest Comments

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

arglebargle commented on 2023-07-28 09:17 (UTC) (edited on 2023-07-28 23:00 (UTC) by arglebargle)

I just ran into the missing glslangValidator build issue as well. If anyone else is building in a chroot and wants a quick fix to get the build moving again I've made an empty package that depends on glslang and creates the glslangValidator symlink using an install script.

https://gist.github.com/foundObjects/5fee314e27d7897212443da8d7db8b5b

I built the above into my aurutils repo then added a glslang-validator-symlink dependency to mesa-git's PKGBUILD and my clean chroot mesa-git builds are moving along nicely again.

Lone_Wolf commented on 2023-07-27 15:23 (UTC) (edited on 2023-07-27 15:23 (UTC) by Lone_Wolf)

https://github.com/KhronosGroup/glslang/pull/3283 https://bugs.archlinux.org/task/79212

Options :

  • Downgrade to glslang 12.2.0
  • create a symlink as described below
  • wait for arch devs to patch this
  • wait for upstream to fix this

rjahanbakhshi commented on 2023-07-27 14:38 (UTC)

@bio3c,

this: https://github.com/KhronosGroup/glslang/issues/47

Based on the changes in the CMakeFile.txt, a symlink must be created for backward compatibilty, but it is not present in the glslang package. I built glslang from source and the symlink is created within the install prefix. Not sure what's going on.

solarisfire commented on 2023-07-27 14:09 (UTC)

ln -s /usr/bin/glslang /usr/bin/glslangValidator

may be a slightly safer workaround...

But thanks for providing that fix bio3c, super helpful!

bio3c commented on 2023-07-27 13:03 (UTC) (edited on 2023-07-27 13:04 (UTC) by bio3c) 

Program glslangValidator found: NO

mesa/meson.build:556:17: ERROR: Program 'glslangValidator' not found or not executable

Couldn't find this change on meson.build upstream... glslang repo recently changed glslang to glslangValidator, cp /usr/bin/glslang /usr/bin/glslangValidator builds just fine...

rjahanbakhshi commented on 2023-07-19 10:42 (UTC)

@edtoml, @Lone_Wolf

Not exactly sure what was wrong, but I sent a fix for the 'pkgver' error when building for staging/23.2. I also tested it with the main branch, and the behavior remains unchanged.

Lone_Wolf commented on 2023-07-17 22:19 (UTC)

@edtoml I've done some more checking and it doesn't look like it is the change in the pkver() function that caused the failure.

branch=staging/23.1 in the sourceurl does work, branch=staging/23.2 fails.

Using commit= with the hashes of the 2 most recent commits of the staging/23.2 branch gives the same result.

I suggest you try to confirm those results.

edtoml commented on 2023-07-16 16:22 (UTC)

(as documented)? Thought I read this this was expected somewhere it the comments. In any case a fix would be very much appriecated. TIA

Lone_Wolf commented on 2023-07-15 15:33 (UTC)

The new pkgver() breaks when not using main (as documented).

It does indeed fail with branch staging/23.2 but I can't pinpoint the cause as it seems to fail upon entering pkgver .

Where can that documentation be found ?

As for adding an extra option for llvm : can be considered when/if someone creates an aur package for it.

edtoml commented on 2023-07-15 13:19 (UTC) (edited on 2023-07-15 13:20 (UTC) by edtoml)

From my POV the new pkgver() is a PITA. I have little to no interest in tracking the main git branch. I do however, like to track the staging/2x.y branch or the tagged rcx versions. The new pkgver() breaks when not using main (as documented). It would be VERY nice if there was a commmented out section in pkgver() which we could enable to let tagged or other branches build. I tracked mesa 23.1-rcx version with no noticed llvm issues. That being said, I have a manually built copy of llvm in $HOME/local/llvmxx (see aur zig-git)- it would be nice if there was a fifth option to easily select this llvm.

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