New package is not suited for use , mesa can currently only use venus-protocol as meson subproject.
venus-protocol support added to PKGBUILD
| 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.027032 |
| First Submitted: | 2014-06-19 21:33 (UTC) |
| Last Updated: | 2026-08-15 16:39 (UTC) |
New package is not suited for use , mesa can currently only use venus-protocol as meson subproject.
venus-protocol support added to PKGBUILD
New package https://aur.archlinux.org/packages/venus-protocol-git created & submitted, working on using it.
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 .
If build fails due to missing venus-protocol dependency for meson just change --wrap-mode=nofallback to --wrap-mode=default
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
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.
I think this package should set -Damdgpu-virtio=true, like the main arch package, otherwise it doesn't work in gpu native contexts
@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.
This patch should fix the API error by just talking directly to the CDN as mentioned by JasonKhew96
diff --git a/PKGBUILD b/PKGBUILD
index fd9d841..68c9ec6 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -121,7 +121,7 @@ declare -A _crates=(
)
for _crate in "${!_crates[@]}"; do
- source+=($_crate-${_crates[$_crate]}.tar.gz::https://crates.io/api/v1/crates/$_crate/${_crates[$_crate]}/download)
+ source+=($_crate-${_crates[$_crate]}.tar.gz::https://static.crates.io/crates/$_crate/${_crates[$_crate]}/download)
done
# NINJAFLAGS is an env var used to pass commandline options to ninja
crates.io now returns 403 due to the rate limit and user agent blocking [0]
should change the download url to static.crates.io [1]
[0] https://crates.io/data-access#api [1] https://github.com/rust-lang/crates.io/issues/13482
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.
Option A - best onesee 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.
Option B - 2nd bestLone_Wolf commented on 2019-07-09 13:43 (UTC) (edited on 2023-04-18 10:41 (UTC) by Lone_Wolf)
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 ?
Lone_Wolf commented on 2018-01-30 14:06 (UTC) (edited on 2023-02-12 11:56 (UTC) by Lone_Wolf)
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 -Bto verify basic OpenGL functionalitybuild lib32-mesa-git
run
glxinfo32 -Bto verify basic OpenGL functionality for multilib programs