Package Details: mesa-git 25.0.0_devel.200442.bfa6b9b6551.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: rjahanbakhshi
Votes: 182
Popularity: 0.47
First Submitted: 2014-06-19 21:33 (UTC)
Last Updated: 2025-01-20 16:09 (UTC)

Required by (1329)

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 11 12 .. 134 Next › Last »

Beiruty commented on 2024-08-08 02:21 (UTC)

@Lone_Wolf I spent a lot of time trying to debug the HW VA by rolling back mes to different releases and branches. I failed to pin the source of regression on any mesa relwase. Since I know for fact that I did not have any regression with prior to 24.x development. I shifted my attention to the kernel, since as a matter of course, it was being upgraded too. I had both Arch-linux main and xanmod1 kernels at 6.10.3. A quick test, I installed mainline lts 6.6.44-3-lts (64-bit), and voila no more crashing or video artifacts.

Next, is that I will try to roll the latest kernel without the regression.

Operating System: EndeavourOS KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.6.44-3-lts (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-2600K CPU @ 3.40GHz Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon HD 7800 Series

Lone_Wolf commented on 2024-08-07 08:57 (UTC) (edited on 2024-08-07 08:58 (UTC) by Lone_Wolf)

@rpi2 You have problems first step of B, revert to mesa repo ? If so you need to post the commands you use and the outputs they give.

Note that your issue is not suited well for aur comments, you may want to use the forums for your distro to ask for help.

@Beiruty

https://man.archlinux.org/man/PKGBUILD.5#USING_VCS_SOURCES

Keep in mind that the 24.2 and main branch are still very close, so 24.2 may also have the issue.

Beiruty commented on 2024-08-07 02:30 (UTC)

With latest mesa-git, I have a regression on HW decode of AVC-1/H264 on my AMD Pitcairn GPU. Any decode of the AVC-1/D264 will show blocks and the GPU will freeze the system.

How do I configure meas-git to get and install mesa 24.2.x branch?

rpi2 commented on 2024-08-07 01:26 (UTC)

Option B, mesa to mesa-git, mesa broke libglvnd dependence「opengl-driver」?

kefaso commented on 2024-07-28 15:34 (UTC)

vainfo fails:

vainfo Trying display: wayland Trying display: x11 libva error: /usr/lib/dri/radeonsi_drv_video.so init failed vaInitialize failed with error code 2 (resource allocation failed),exit

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 ?

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