Package Details: mesa-git 25.2.0_devel.205654.033ce1bae15.d41d8cd-2

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: Lone_Wolf
Votes: 189
Popularity: 1.23
First Submitted: 2014-06-19 21:33 (UTC)
Last Updated: 2025-05-17 15:47 (UTC)

Dependencies (52)

Required by (1368)

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 .. 17 18 19 20 21 22 23 24 25 26 27 .. 136 Next › Last »

DoomerCat commented on 2023-10-30 20:57 (UTC)

A Merge Request broke steam

https://gitlab.freedesktop.org/mesa/mesa/-/issues/10059

rjahanbakhshi commented on 2023-10-30 08:35 (UTC)

@therealmate, @Lone_Wolf,

Enabling gallium-opencl and a clean chroot build was successful, so I'm enabling it again.

Lone_Wolf commented on 2023-10-27 18:44 (UTC)

@therealmate The reason for disabling opencl was a build dailure with all llvm trunk variants.

https://gitlab.freedesktop.org/mesa/mesa/-/issues/8591 has been closed, so opencl should build again.

Maybe you could enable it and test if mesa-git builds succesfully ?

therealmate commented on 2023-10-26 20:40 (UTC)

Is "libclc" needed? As i see, this package (libclc) is needed for opencl, which is disabled (gallium-opencl=disabled)

Lone_Wolf commented on 2023-10-26 20:09 (UTC)

Yes, that is expected.

The gallium-drivers & vulkan-drivers this package builds for are carefully selected and only work on x86_64 architecture .

In theory we could use the auto feature for gallium-drivers / vulkan-drivers to let mesa decide what drivers are built.

Aside from losing control over which drivers are build this would require running tests on atleast x86_64 & arm64/aarch64 architectures.

Then there is the question of dependencies : currently mesa-git supports 4 llvm variants. Even if there are arm64/aarch64 counterparts for all of them, adding them would further complicate an already complicated PKGBUILD.

It seems much easier if someone knowledgable with arm64 tooling & system packages starts a separate package and hosts it somewhere.

PseudoSpock commented on 2023-10-26 19:11 (UTC)

Is it normal this won't build for arm64/aarch64?

Lone_Wolf commented on 2023-10-01 09:51 (UTC) (edited on 2023-10-08 20:21 (UTC) by Lone_Wolf)

Building mesa is currently broken with meson 1.2.2 , don't upgrade that package for the time being.

see https://gitlab.freedesktop.org/mesa/mesa/-/issues/9908 and https://bugs.archlinux.org/task/79821

The issue also affected repo mesa and the repo meson package is patched to work for building mesa. Upgrade to meson 1.2.2-2 works fine.

Lone_Wolf commented on 2023-09-20 19:49 (UTC)

the /src/intel is probably not what caused the build failure but just the job that ran the longest after the error occurred.

Post the build log somewhere public, see https://wiki.archlinux.org/title/List_of_applications#Without_a_dedicated_client for a few options.

d3vilguard commented on 2023-09-20 10:35 (UTC) (edited on 2023-10-06 12:19 (UTC) by d3vilguard)

[FIXED] EDIT 10.06.23 As @Lone_Wolf had mentioned, there is a issue with meson 1.2.2. Building in a clean chroot using llvm-minimal-git but with downgraded meson to 1.2.1 builds mesa-git without failing.

[Original comment] Building in a clean chroot after having built llvm-minimal-git. Build fails:

[1026/2687] Compiling C object src/intel/perf/libintel_perf.a.p/meson-generated_.._intel_perf_metrics.c.o ninja: build stopped: subcommand failed. ==> ERROR: A failure occurred in build(). Aborting...

« First ‹ Previous 1 .. 17 18 19 20 21 22 23 24 25 26 27 .. 136 Next › Last »