Package Details: mesa-git 25.2.0_devel.206777.7bfb51a7e6f.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-clover-mesa, opencl-rusticl-mesa, vulkan-intel, vulkan-mesa-layers, vulkan-nouveau, vulkan-radeon, vulkan-swrast, vulkan-virtio
Provides: libva-mesa-driver, mesa, mesa-libgl, mesa-vdpau, opencl-driver, opencl-rusticl-mesa, opengl-driver, vulkan-driver, vulkan-intel, vulkan-mesa-layers, vulkan-nouveau, vulkan-radeon, vulkan-swrast, vulkan-virtio
Submitter: Krejzi
Maintainer: rjahanbakhshi (Lone_Wolf)
Last Packager: rjahanbakhshi
Votes: 189
Popularity: 1.05
First Submitted: 2014-06-19 21:33 (UTC)
Last Updated: 2025-06-12 14:46 (UTC)

Required by (1370)

Sources (6)

Pinned Comments

Lone_Wolf commented on 2024-09-10 19:58 (UTC)

removed obsolete options, build now works again.

building opencl clover is disabled for now, see https://gitlab.freedesktop.org/mesa/mesa/-/issues/11863

Those that need opencl should use rusticl instead. Note that rusticl at runtime is disabled by default, see https://docs.mesa3d.org/envvars.html#rusticl-environment-variables for info about enabling it.

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

« First ‹ Previous 1 .. 36 37 38 39 40 41 42 43 44 45 46 .. 136 Next › Last »

libgradev commented on 2021-08-13 14:57 (UTC)

The explicit mention of ACO has been removed from the deviceName / driverInfo strings due to it now being the default.

It will, however, still show LLVM when forced: driverInfo = Mesa 21.3.0-devel (git-01b0935d31) (LLVM 12.0.1)

juftuf commented on 2021-08-06 20:51 (UTC)

It's a mesa issue then. Performance loss is notable.

Lone_Wolf commented on 2021-08-06 20:34 (UTC)

mesa trunk built against llvm-minimal-git 13.0.0_r394679.c261a06b7a98-1 (from /var/cache/pacman/pkg dated july 24) also doesn't show ACO , so I think this is due to a change in mesa sourcecode.

Will search for that, but have you noticed anything outside of vulkaninfo that indicates vulkan is performing worse then before ?

juftuf commented on 2021-08-06 13:55 (UTC)

It's runtime issue. Builds just fine. Checking if aco compiler is active with vulkantools: vulkaninfo | grep deviceName

Which returns you the loaded icd-driver and currently active compiler. Should look like this "deviceName = AMD RADV SIENNA_CICHLID (ACO)"

When building against newest llvm-package it's missing the compiler and only returning. "deviceName = AMD RADV SIENNA_CICHLID"

If forcing the compiler via environmental variable "RADV_DEBUG=llvm" it's loading llvm correctly. "deviceName = AMD RADV SIENNA_CICHLID (LLVM 14.0.0)"

Lone_Wolf commented on 2021-08-06 10:15 (UTC)

Will look into it, are the issues at buildtime or at runtime ?

If at runtime, how do you test aco ?

juftuf commented on 2021-08-05 16:59 (UTC)

I can't get ACO-compiler to work when building against the llvm-minimal-git-14.0.0_r395861 trunk master. Was still working with llvm-minimal-git-13. Is there something that I've missed?

rjahanbakhshi commented on 2021-06-20 12:59 (UTC)

Crocus gallium driver added to the PKGBUILD.

kprkpr commented on 2021-06-20 12:09 (UTC)

Hi! In newer mesa drivers, there is a new gallium driver, crocus You can enable at PKGBUILD? I tried and works good Thanks :)

" -D gallium-drivers=r300,r600,radeonsi,nouveau,svga,swrast,virgl,iris,zink,crocus \"

pepster commented on 2021-06-16 19:46 (UTC)

How embarrassing. Yes, I did that some time ago but was not at my pc for some weeks and totally forgot about that. Shame on me, my deepest apologies. Should have checked the first lines of my own logfile :-(

Thank you for your time and sorry for wasting it.

Lone_Wolf commented on 2021-06-16 18:23 (UTC) 

C compiler for the host machine: clang (clang 12.0.0 "clang version 12.0.0")
C linker for the host machine: clang ld.bfd 2.36.1
C++ compiler for the host machine: clang++ (clang 12.0.0 "clang version 12.0.0")
C++ linker for the host machine: clang++ ld.bfd 2.36.1

On archlinux default complier is cc / c++ currently gcc 11.10 .

I just tested in a clean chroot with gcc and there is no error for that target reported .

Has manjaro switched default compiler to clang or did you make that change yourself ?

« First ‹ Previous 1 .. 36 37 38 39 40 41 42 43 44 45 46 .. 136 Next › Last »