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

Dependencies (53)

Required by (1314)

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 2 3 4 5 6 7 8 9 10 .. 131 Next › Last »

rjahanbakhshi commented on 2024-07-25 05:33 (UTC)

@grumpynaga,

https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30311 is merged upstream. Removed from PKGBUILD. Thanks,

grumpynaga commented on 2024-07-25 02:33 (UTC) (edited on 2024-07-25 02:36 (UTC) by grumpynaga)

Fails to build for me currently

==> Making package: mesa-git 24.3.0_devel.192434.c30e5d44b10.27daf3f-1 (Do 25 Jul 2024 04:35:48 CEST)

  -> Extracting proc-macro2-1.0.70.tar.gz with bsdtar
  -> Extracting unicode-ident-1.0.12.tar.gz with bsdtar
  -> Extracting quote-1.0.33.tar.gz with bsdtar
  -> Extracting syn-2.0.39.tar.gz with bsdtar
==> Starting prepare()...
Applying patch 30311.patch...
patching file src/gallium/targets/dril/dril_target.c
Reversed (or previously applied) patch detected!  Skipping patch.
5 out of 5 hunks ignored -- saving rejects to file src/gallium/targets/dril/dril_target.c.rej
==> ERROR: A failure occurred in prepare().
    Aborting...
 -> error making: mesa-git-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
mesa-git - exit status 4

rjahanbakhshi commented on 2024-07-24 11:30 (UTC)

@Lone_Wolf,

That is correct. Meanwhile, I added softpipe to keep the compatibility intact.

yurikoles commented on 2024-07-24 11:03 (UTC)

@Lone_Wolf

Oh, I'm sorry for bothering, that really makes sense. I said this when I was deeply in the context of my WIP Homebrew mesa 24.2.0 branch for macOS, where we can't enable any gallium drivers except softpipe.

Lone_Wolf commented on 2024-07-24 10:36 (UTC)

@yurikoles :

I guess reza copied my change in mesa-minimal-git and I dropped softpipe intentionally .

The mr that deprecated gallium swrast (which is not the same as vulkan swrast) and split it into softpipe + llvmpipe made clear the reason for it was to make it possible to stop building softpipe .

Are you aware of use cases for gallium softpipe ?

yurikoles commented on 2024-07-24 08:58 (UTC) (edited on 2024-07-24 09:58 (UTC) by yurikoles)

Hi Reza,

swrast => softpipe + llvmpipe

So you effectively dropped softpipe.

Beiruty commented on 2024-07-24 02:43 (UTC)

I upgraded to the latest meas-git (build against llvm from extra, option 4). After the upgrade, Arch/KDE plasma 6.1.3 could not go into graphical mode. It was stuck at the fast blinking cursor. I timeshift back to a working version of mesa-git. Now, I am installing. llvm-minimal-git and I will be building against option 1. I hope it works, if not, I have to file a regression buy report.

ArchUsr1 commented on 2024-07-23 15:56 (UTC)

Build error mesa/meson.build:961:2: ERROR: Problem encountered: Python (3.x) yaml module (PyYAML) required to build mesa.

I think it's related to what @atticf mentioned

A full log can be found at /build/mesa-git/src/_build/meson-logs/meson-log.txt
==> ERROR: A failure occurred in build().
    Aborting...
==> ERROR: Build failed, check /var/lib/aurbuild/x86_64/user/build
error: failed to build 'mesa-git-24.2.0_devel.191080.cdd604583f6.d41d8cd-1': failed to run: makechrootpkg -r /var/lib/aurbuild/x86_64 -d /var/cache/pacman/pkg/ -- -feA --noconfirm --noprepare --holdver: 
error: packages failed to build: mesa-git-24.2.0_devel.191080.cdd604583f6.d41d8cd-1

Lone_Wolf commented on 2024-07-23 10:43 (UTC) (edited on 2024-07-23 10:46 (UTC) by Lone_Wolf)

It may be that the pkgver in .SRCINFO is not the same as that in PKGBUILD, but the dependencies in .SRCINFO are correct.

Also these are VCS packages which always build the latest avaialble version, so pkgver is dynamic and established at runtime .

The pkgver value shown on this page only reflects the version that was used when last update for this package was committed and has no other relevance .

Have you tried building in a new folder with freshly cloned PKGBUILD & other files ?

multi.flexi commented on 2024-07-22 14:17 (UTC)

pkgver in PKGBUILD and package name on top of the page do not match. This causes issues, paru or yay build older version with older llvm/llvm-libs.

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