Package Details: mesa-git 21.1.0_devel.135859.a1e9a5d6534-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 X11
Licenses: custom
Conflicts: libva-mesa-driver, mesa, mesa-vdpau, opencl-mesa, vulkan-intel, vulkan-mesa-layer, vulkan-radeon, vulkan-swrast
Provides: libva-mesa-driver, mesa, mesa-vdpau, opencl-driver, opencl-mesa, opengl-driver, vulkan-driver, vulkan-intel, vulkan-mesa-layer, vulkan-radeon, vulkan-swrast
Submitter: Krejzi
Maintainer: Lone_Wolf (rjahanbakhshi)
Last Packager: rjahanbakhshi
Votes: 163
Popularity: 1.27
First Submitted: 2014-06-19 21:33
Last Updated: 2021-03-03 09:02

Dependencies (34)

Required by (1000)

Sources (3)

Pinned Comments

Lone_Wolf commented on 2021-01-03 15:38

I am using another package now and am looking for a new maintainer.

Lone_Wolf commented on 2020-04-23 12:26

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

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

AUR helpers like yay and pamac can't deal with such a dynamic choice. People who use those will have to accept the default of building mesa-git against stock repo packages.

Lone_Wolf commented on 2018-01-30 14:06

  • issues
Simple issues can be dealth with through aur comments, but sometimes discussion is needed.
Use https://bbs.archlinux.org/viewtopic.php?id=212819 for that.
  • 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 , restart X .

run glxinfo to verify basic OpenGL functionality

build lib32-mesa-git

run glxinfo32 to verify basic OpenGL functionality for multilib programs

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 ... Next › Last »

gort818 commented on 2020-05-14 22:47

@Lone_Wolf I have already filed a bug report.

My system only has one vulkan capable card.

I tired MESA_VK_DEVICE_SELECT=0 for good measure and no luck.

Lone_Wolf commented on 2020-05-14 09:59

@gort818 Mesa 20.1 (currently in rc phase) will support that option, could you file bugreports ?

Does your system have one or more vulkan capable cards ?

If more then one, try MESA_VK_DEVICE_SELECT=list vulkaninfo to find out which ids the cards have.

You should then be able to assign a specific one to the game which may solve the issue.

gort818 commented on 2020-05-14 03:07

vulkan-device-select-layer=true has caused issues launching some of my games, after I set it to false no problems.

Lone_Wolf commented on 2020-05-08 20:43

Mesa-git is currently broken on some types of cards (including all polaris10 /RX580 ).

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

Solved with https://gitlab.freedesktop.org/mesa/mesa/-/commit/1a59590e5d686a11687151d57f2fd43d366d6720

Lone_Wolf commented on 2020-05-02 14:34

I guess that should be possible, though i'm not sure of the benefits.

Maybe glamor / modesetting improvements ?

sinatosk commented on 2020-05-02 11:42

adding 'mesa-libgl' to 'provides' allows me to compile and install package 'xorg-server' without having to install official packages 'mesa' and 'lib32-mesa'

Lone_Wolf commented on 2020-04-29 11:55

libclc requires hardware specific files in /usr/lib/clc .

My card is a RX 580 of polaris 10 family.

The gfx1010 suggest you have an RX 5xxx / Navi videocard ? libclc doesn't support those and may never do that.

Unfortunately rocm also doesn't seem to support them, so amd proprietary driver from opencl-amd is your only choice for opencl.

tb0n3 commented on 2020-04-28 23:28

I've never been able to use the opencl that builds with mesa-git in the applications I have. I've tried running GPU calculations with Folding@Home, and benchmarking hashcat and they both fail unless I use the amdgpu driver version in the opencl-amd package. The failure message I get is in the code block below. Have you seen similar results? clinfo reports the mesa version is OpenCL 1.1.


clBuildProgram(): CL_BUILD_PROGRAM_FAILURE

fatal error: cannot open file '/usr/lib/clc/gfx1010-amdgcn-mesa-mesa3d.bc': No such file or directory

* Device #1: Kernel /usr/share/hashcat/OpenCL/shared.cl build failed.

clinfo results in a very similar error.


=== CL_PROGRAM_BUILD_LOG ===
fatal error: cannot open file '/usr/lib/clc/gfx1010-amdgcn-mesa-mesa3d.bc': No such file or directory
  Preferred work group size multiple              <getWGsizes:1200: create kernel : error -46>

Lone_Wolf commented on 2020-04-27 23:57

Build failure solved, see https://gitlab.freedesktop.org/mesa/mesa/-/commit/42b1696ef627a5bfee29911a780fa0a4dbf04610

Lone_Wolf commented on 2020-04-26 15:26

mesa master fails to build against lastest llvm trunk

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