Package Details: mesa-git 24.3.0_devel.194818.d3429a7e00d.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: Lone_Wolf
Votes: 182
Popularity: 0.47
First Submitted: 2014-06-19 21:33 (UTC)
Last Updated: 2024-09-15 20:40 (UTC)

Dependencies (53)

Required by (1302)

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 .. 13 14 15 16 17 18 19 20 21 22 23 .. 131 Next › Last »

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

laichiaheng commented on 2023-08-29 12:56 (UTC)

The clang and llvm version on Arch Linux has been updated

ruabmbua commented on 2023-08-28 21:07 (UTC)

I am experiencing segfaults with e.g. vkcube-wayland, and really any other vulkan + wayland client. Its segfaulting when trying to create the swapchain.

Anyone else experiencing this, or any ideas?

As a reference: https://github.com/gfx-rs/wgpu/issues/4095

solarisfire commented on 2023-08-20 17:42 (UTC) (edited on 2023-08-20 17:44 (UTC) by solarisfire)

Yes it has been, but a lot of the code has since been updated by other commits.

laichiaheng commented on 2023-08-20 17:39 (UTC)

Hi, I have a question. Does it contain the following commit?

https://gitlab.freedesktop.org/mesa/mesa/-/commit/6674ac98a6abe5f325df43671114e6d9d7483207

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.

« First ‹ Previous 1 .. 13 14 15 16 17 18 19 20 21 22 23 .. 131 Next › Last »