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 (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 .. 74 75 76 77 78 79 80 81 82 83 84 .. 131 Next › Last »

gentoofu commented on 2016-10-22 00:13 (UTC)

For mesa-vulkan-intel-git-13.1.0_devel.85935.8ff4182-1, commenting the following line in PKGBUILD should resolve the issue: mv -v ${srcdir}/fakeinstall/usr/share/vulkan/icd.d/intel_icd.json ${pkgdir}/usr/share/vulkan/icd.d

omni commented on 2016-10-13 15:04 (UTC)

thank you for your time and the link, mesa-git is working again. Installing lib32-lm_sensors solved it.

Lone_Wolf commented on 2016-10-12 20:51 (UTC)

There are several differences between AUR mesa-git and Lordheavy's [mesa-git] repo, see https://bbs.archlinux.org/viewtopic.php?id=212819 the most common reason for glxinfo / glxinfo32 failing : mesa was build against a llvm version that is no no longer installed. One way this can occur is if mesa-git/llvm-svn are updated but their lib32 counterparts aren't (reverse is also true).

omni commented on 2016-10-12 17:36 (UTC)

rolled back to non git. i think the devs will fix this soon, retry it in a couple of days...

smirky commented on 2016-10-12 17:29 (UTC)

Never mind, I actually rebuilt it myself, without doing modifications, installed all the packages and now it works just fine. Honestly, I don't see why my build works and the [mesa-git] doesn't, but at least I got it working. I guess [mesa-git] has nothing to do with this package?

smirky commented on 2016-10-12 15:51 (UTC)

OK, so I have this: 0 « smirky » ~ » glxinfo32 name of display: :0 libGL error: unable to load driver: radeonsi_dri.so libGL error: driver pointer missing libGL error: failed to load driver: radeonsi libGL error: unable to load driver: radeonsi_dri.so libGL error: driver pointer missing libGL error: failed to load driver: radeonsi libGL error: unable to load driver: swrast_dri.so libGL error: failed to load driver: swrast X Error of failed request: GLXBadContext Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 6 (X_GLXIsDirect) Serial number of failed request: 55 Current serial number in output stream: 54 What now? I proved that one of that the glxinfo tools cannot work with mesa-git (lib32?) 1 « smirky » ~ » pacman -Q|grep mesa lib32-mesa-demos 8.3.0-2 lib32-mesa-git 85559.cfbf956-1 lib32-mesa-libgl-git 85559.cfbf956-1 mesa-demos 8.3.0-2 mesa-git 85559.cfbf956-1 mesa-libgl-git 85559.cfbf956-1 opencl-mesa-git 85559.cfbf956-1 I'm using the "amdgpu" driver.

omni commented on 2016-10-12 15:24 (UTC)

seems it is not steam, glxinfo32 fails... http://pastebin.com/JRF82xmE noone else having this?

Lone_Wolf commented on 2016-10-11 20:48 (UTC)

omni, there are other reasons why that can fail. Next time that happens run glxinfo & glxinfo32 . If either fails, the cause of the problem is NOT steam.

omni commented on 2016-10-11 15:38 (UTC)

after last update steam got typically swrast, libgl errors. Known problem, known solution. but this time the fixes (in short here: https://dschense.de/archlinux-steam-fix/) doesn't work. after downgrading to non git version steam started again. maybe interesting...

« First ‹ Previous 1 .. 74 75 76 77 78 79 80 81 82 83 84 .. 131 Next › Last »