Package Details: mesa-git 26.3.0_devel.228038.f0bcf544881.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, opencl-clover-mesa, opencl-rusticl-mesa, vulkan-intel, vulkan-mesa-device-select, vulkan-mesa-implicit-layers, vulkan-mesa-layers, vulkan-nouveau, vulkan-radeon, vulkan-swrast, vulkan-virtio
Provides: libva-mesa-driver, mesa, mesa-libgl, opencl-driver, opencl-rusticl-mesa, opengl-driver, vulkan-driver, vulkan-intel, vulkan-mesa-device-select, vulkan-mesa-implicit-layers, vulkan-mesa-layers, vulkan-nouveau, vulkan-radeon, vulkan-swrast, vulkan-virtio
Submitter: Krejzi
Maintainer: rjahanbakhshi (Lone_Wolf)
Last Packager: Lone_Wolf
Votes: 192
Popularity: 0.018366
First Submitted: 2014-06-19 21:33 (UTC)
Last Updated: 2026-08-15 16:39 (UTC)

Required by (2196)

Sources (9)

Pinned Comments

Lone_Wolf commented on 2024-09-10 19:58 (UTC) (edited on 2026-08-11 15:58 (UTC) by Lone_Wolf)

rusticl is now provided by opencl-mesa.

Note that only a few hardware drivers are supported by default, see https://docs.mesa3d.org/envvars.html#rusticl-environment-variables for info about enabling others.

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 .. 139 Next › Last »

SpacingBat3 commented on 2026-08-26 17:17 (UTC) (edited on 2026-08-26 17:18 (UTC) by SpacingBat3)

Hmm, I wonder if anyone did propose this before but have you (@rjahanbakhshi and @Lone_Wolf) considered making this a split package? I see more than a few benefits from that change:

  1. It could follow Arch mesa package set, with extra/mesa package being a loader, not entire implementation, allowing for more modular implementations. This would feel more natural for users expecting AUR mesa-git to offer same package set and that would like to install both mesa-git. Right now AUR has some standalone packages that, at first glance, seem like part of mesa-git but aren't.

  2. LLVM could as well be tied up to some mutually exclusive metapackage set, like mesa-llvm-provider-* as a build dep and specialize it towards more specific llvm provider flavor as package dep, which would move the env-based LLVM picking towards pacman dependency-based solution that probably would also be more robust solution with AUR helpers.

For also implementing (1) I am pretty sure this would require further discussing with, or at least informing, other AUR maintainers and removing those packages to migrate towards mesa-git provided split. It could also introduce some maintenance burden as most likely the package separation would have to be handled on PKGBUILD side than on upstream, I don't think mesa has that kind of installation infrastructure and I believe this is also being done in Arch mesa PKGBUILD. Some could also argue about new packages that needs to be introduced over time, but if we track all installation files that are expected to be placed for a given package (even as a directory, recursively), I can see it could be handled either in failing or non-failing (e.g. special package and warning) way, depending on what would be preferred method to do so

This is just currently a brief of the concept I had in mind, not sure if I had missed other implications with it, I didn't really thought or experimented with it that much yet. Maybe it is something that others have asked before, maybe some pinned comment could clarify it?

Lone_Wolf commented on 2026-08-12 12:15 (UTC)

New package is not suited for use , mesa can currently only use venus-protocol as meson subproject.

venus-protocol support added to PKGBUILD

Lone_Wolf commented on 2026-08-11 15:57 (UTC)

New package https://aur.archlinux.org/packages/venus-protocol-git created & submitted, working on using it.

Lone_Wolf commented on 2026-08-07 20:28 (UTC)

Using --wrap-mode=default is a bad idea as you loose control and allow meson to download anything it detects as 'missing' which has a high chance of pulling in unwanted stuff.

Adding support for the venus-protocol requires a new package. For aur that's blocked and since venus-protocol became a dep in master just 4 days ago and is not included in 26.2 arch devs have no need to add it to extra.

Removing virtio from the vulkan-drivers line is much simpler and has no bad consequences apart from loosing vulkan support in VMs .

quark23 commented on 2026-08-07 06:34 (UTC)

If build fails due to missing venus-protocol dependency for meson just change --wrap-mode=nofallback to --wrap-mode=default

cookiecaper commented on 2026-07-13 02:43 (UTC) (edited on 2026-07-17 18:32 (UTC) by cookiecaper)

Note that builds in the last day or so include a patch that detects the broken libclc distributed with LLVM 22.x and prevents the compilation of OpenCL kernels that rely on it. If your OpenCL support suddenly stopped working, maybe that's why.

There's an issue here with a patch for libclc that'll fix the issue: https://gitlab.archlinux.org/archlinux/packaging/packages/libclc/-/work_items/13

EDIT: I made an AUR package with the patch: https://aur.archlinux.org/packages/libclc-patch-broken-flush-denormal

Lone_Wolf commented on 2026-06-28 11:39 (UTC)

Note that the gallium virgl and vulkan virtio driver are build so it's not like mesa-git has no support for VMs.

If we add -D amdgpu-virtio=true we should also add -D intel-virtio-experimental=true to ensure both amd and intel are supported.

BadAtNames commented on 2026-06-27 22:26 (UTC)

I think this package should set -Damdgpu-virtio=true, like the main arch package, otherwise it doesn't work in gpu native contexts

https://gitlab.archlinux.org/archlinux/packaging/packages/mesa/-/blob/main/PKGBUILD?ref_type=heads#L252

rjahanbakhshi commented on 2026-06-03 05:50 (UTC)

@LandonDeam, @JasonKhew96, @linkmauve,

Thanks for your comments. Python is no longer a runtime dependency. crates.io download is now pointing to CDN to avoid the rate-limit problem.

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