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.39
First Submitted: 2014-06-19 21:33 (UTC)
Last Updated: 2024-09-15 20:40 (UTC)

Dependencies (53)

Required by (1306)

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 .. 20 21 22 23 24 25 26 27 28 29 30 .. 131 Next › Last »

sclu1034 commented on 2023-01-24 20:52 (UTC)

0002-intel-fs-always-mask-the-bottom-bits-of-the-sampler-.patch does not apply anymore, failing the build. Building commit 81b5f6a3fd570a3a0c4fab2b8a83eb41928dbc98.

The reject is:

--- src/intel/vulkan/genX_cmd_buffer.c
+++ src/intel/vulkan/genX_cmd_buffer.c
@@ -5955,6 +5955,11 @@ genX(flush_pipeline_select)(struct anv_cmd_buffer *cmd_buffer,
    }
 #endif

+#if GFX_VERx10 == 120
+   if (pipeline == _3D)
+      cmd_buffer->state.compute.pipeline_dirty = true;
+#endif
+
    /* From "BXML » GT » MI » vol1a GPU Overview » [Instruction]
     * PIPELINE_SELECT [DevBWR+]":
     *

Lone_Wolf commented on 2023-01-18 13:31 (UTC)

That is expected behaviour.

Consensus amongst archlinux devs & users is that WSL2-exclusive features are useless on archlinux and thus disabled/not included in build options.

You'll have to build your own mesa version for wsl2 support. Check at the place where you downloaded the image to install arch on WSL2, maybe they already have such a package.

niqingliang2003 commented on 2023-01-17 08:49 (UTC)

I'm using Arch under WSL, and want to use vulkan, which depend on dzn_icd.x86_64.json. but I can't find this file.

rjahanbakhshi commented on 2023-01-09 19:27 (UTC)

@yurikoles,

The changes are pushed now. Thanks,

yurikoles commented on 2023-01-09 19:24 (UTC)

Thanks for the report, I removed the patch.

Did you forget to push your changes?

rjahanbakhshi commented on 2023-01-09 18:56 (UTC)

@Billli11,

Thanks for the report, I removed the patch.

Billli11 commented on 2023-01-09 18:20 (UTC) (edited on 2023-01-09 18:22 (UTC) by Billli11)

Currently the patch 0001-anv-force-MEDIA_INTERFACE_DESCRIPTOR_LOAD-reemit-aft.patch is failed to apply.

Most likely cause by commit 1067ec90a591b26a0d6c9b298b1a894bb0a66836

==> Starting prepare()...
Applying patch 0001-anv-force-MEDIA_INTERFACE_DESCRIPTOR_LOAD-reemit-aft.patch...
patching file src/intel/vulkan/genX_cmd_buffer.c
Hunk #1 FAILED at 5955.
1 out of 1 hunk FAILED -- saving rejects to file src/intel/vulkan/genX_cmd_buffer.c.rej
==> ERROR: A failure occurred in prepare().
    Aborting...

the package can be compiled without it.

yurikoles commented on 2022-12-28 14:11 (UTC)

@j_klee

You may install package after build with makepkg -i inside a directory with wanted PKGBUILD. It has the same effect as running pacman -U <built_package>.pkg.tar.zst.

But such a basic questions is out of the scope of this support page, which is for issues that are specific to mesa-git. ArchLinux users are advised to read wiki before asking for help, e.g. here is a page about AUR.

j_klee commented on 2022-12-27 12:27 (UTC)

Hi, I try to install with Option B, but am struggling with it.

  • I installed llvm-minimal-git.
  • I installed mesa (from Extra)
  • I build mesa-git
  • I now have the build file *pkg.tar.zst and don't know what to do with it.

How to switch from mesa to mesa-git? I found this lin https://bbs.archlinux.org/viewtopic.php?id=58277 and tried to use -d with pacman without success.

« First ‹ Previous 1 .. 20 21 22 23 24 25 26 27 28 29 30 .. 131 Next › Last »