Package Details: mesa-git 24.2.0_devel.188655.894f7f43874.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-clover-mesa, 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: rjahanbakhshi
Votes: 179
Popularity: 1.88
First Submitted: 2014-06-19 21:33 (UTC)
Last Updated: 2024-05-02 05:24 (UTC)

Required by (1241)

Sources (6)

Pinned Comments

Lone_Wolf commented on 2024-04-03 16:59 (UTC)

To those with the directx errors : archlinux directx-headers pacakgae is 2 releases behind upstream. Try building against aur directx-headers-git .

I don't remember what d3d12 does, but offical mesa also supports it.

@ZephyrCheez : thanks, that option lead to meson subprojects and mesa sourcetree does appear to include the data needed to use them. Adding nouveau vulkan looks doable now, no idea when there will be time to implement it.

Lone_Wolf commented on 2024-02-20 00:09 (UTC) (edited on 2024-02-20 00:11 (UTC) by Lone_Wolf)

@Beiruty, those have the same cause as the other recent build failures : changes in intel drivers.

The build issues caused by changes in intel drivers are now solved for MESA_WHICH_LLVM 1, 3 and 4 (llvm-minimal-git , llvm from lordheavy unofficial repo and offical repo llvm )

MESA_WHICH_LLVM 2 (aur llvm-git) build is still broken, but I MAY have a solution for that without having to create new packages.

The good news is that once all 4 variants built again, only minor changes should be needed to add opencl clover & opencl rusticl support.

(A lot of the work required to built the intel drivers is also useful for clover & rusticl)

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 .. 72 73 74 75 76 77 78 79 80 81 82 .. 126 Next › Last »

yurikoles commented on 2016-04-30 08:10 (UTC)

Last error was solved by upgrading llvm-svn. Consider putting svn rev in deps.

yurikoles commented on 2016-04-30 07:28 (UTC)

Now I see antoher error: https://gist.github.com/yurikoles/1c6436c772b647fc3e6c74eca645ff09

Lone_Wolf commented on 2016-04-29 14:20 (UTC)

yurikoles,the cause of your error is probably listed above what you posted. no errors here building 11.3.0_devel.80817.c750029 , please try again.

yurikoles commented on 2016-04-29 13:54 (UTC)

make[6]: *** Waiting for unfinished jobs.... /usr/bin/mkdir -p '/home/yurikoles/work/mesa-git/src/fakeinstall/usr/lib' /usr/bin/mkdir -p '/home/yurikoles/work/mesa-git/src/fakeinstall/etc/vulkan/icd.d' /bin/sh ../../../libtool --mode=install /usr/bin/install -c libvulkan_intel.la '/home/yurikoles/work/mesa-git/src/fakeinstall/usr/lib' /usr/bin/mkdir -p '/home/yurikoles/work/mesa-git/src/fakeinstall/usr/include/vulkan' /usr/bin/install -c -m 644 intel_icd.json '/home/yurikoles/work/mesa-git/src/fakeinstall/etc/vulkan/icd.d' /usr/bin/install -c -m 644 ../../../include/vulkan/vk_platform.h ../../../include/vulkan/vulkan.h ../../../include/vulkan/vulkan_intel.h '/home/yurikoles/work/mesa-git/src/fakeinstall/usr/include/vulkan' libtool: install: /usr/bin/install -c .libs/libvulkan_intel.so /home/yurikoles/work/mesa-git/src/fakeinstall/usr/lib/libvulkan_intel.so libtool: install: /usr/bin/install -c .libs/libvulkan_intel.lai /home/yurikoles/work/mesa-git/src/fakeinstall/usr/lib/libvulkan_intel.la libtool: warning: remember to run 'libtool --finish /usr/lib' make[6]: Leaving directory '/home/yurikoles/work/mesa-git/src/mesa/src/intel/vulkan' Makefile:1826: recipe for target 'install-am' failed make[5]: *** [install-am] Error 2 make[5]: Leaving directory '/home/yurikoles/work/mesa-git/src/mesa/src/intel/vulkan' Makefile:1660: recipe for target 'install-recursive' failed make[4]: *** [install-recursive] Error 1 make[4]: Leaving directory '/home/yurikoles/work/mesa-git/src/mesa/src/intel/vulkan' Makefile:1820: recipe for target 'install' failed make[3]: *** [install] Error 2 make[3]: Leaving directory '/home/yurikoles/work/mesa-git/src/mesa/src/intel/vulkan' Makefile:550: recipe for target 'install-recursive' failed make[2]: *** [install-recursive] Error 1 make[2]: Leaving directory '/home/yurikoles/work/mesa-git/src/mesa/src/intel' Makefile:690: recipe for target 'install-recursive' failed make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory '/home/yurikoles/work/mesa-git/src/mesa/src' Makefile:639: recipe for target 'install-recursive' failed make: *** [install-recursive] Error 1 ==> ERROR: A failure occurred in build(). Aborting...

Lone_Wolf commented on 2016-04-28 22:10 (UTC)

vulkan support re-enabled. Thanks, FadeMind.

FadeMind commented on 2016-04-28 18:04 (UTC)

BUG 95182 was fixed in https://cgit.freedesktop.org/mesa/mesa/commit/?id=6028a67641741cb4e14265440282481441efa9c8

Lone_Wolf commented on 2016-04-28 11:49 (UTC) (edited on 2016-04-28 12:53 (UTC) by Lone_Wolf)

the patch is indeed no longer needed, but i found a new vulkan bug : https://bugs.freedesktop.org/show_bug.cgi?id=95182 uploaded new version with vulkan support commented out.

kerberizer commented on 2016-04-26 22:37 (UTC)

@Lone_Wolf, it seems @lcarlier's patch has been finally committed upstream... https://cgit.freedesktop.org/mesa/mesa/commit/?id=12cf08fcc3e3229ce8b4f8f9b3230388b16a7e62

Lone_Wolf commented on 2016-04-20 08:56 (UTC)

FadeMind, it was mesa-git that installed files that are also provided by vulkan-headers, not mesa-vulkan-intel-git . mesa-git now removes those duplicate files.

FadeMind commented on 2016-04-20 04:39 (UTC)

Please fix conflicts for mesa-vulkan-intel-git provides=('vulkan-intel' 'vulkan-headers') replaces=('vulkan-intel' 'vulkan-headers') conflicts=('vulkan-intel' 'vulkan-headers') against (...) error: failed to commit transaction (conflicting files) mesa-git: /usr/include/vulkan/vk_platform.h exists in filesystem mesa-git: /usr/include/vulkan/vulkan.h exists in filesystem Errors occurred, no packages were upgraded. ==> WARNING: Failed to install built package(s). ==> Cleaning up... $ pacman -Qo /usr/include/vulkan/vk_platform.h /usr/include/vulkan/vk_platform.h is owned by vulkan-headers 1.0.20160415-1 regards

« First ‹ Previous 1 .. 72 73 74 75 76 77 78 79 80 81 82 .. 126 Next › Last »