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.56
First Submitted: 2014-06-19 21:33 (UTC)
Last Updated: 2025-01-20 16:09 (UTC)

Required by (1313)

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

1 2 3 4 5 6 .. 133 Next › Last »

Billli11 commented on 2025-01-18 14:39 (UTC) (edited on 2025-01-18 14:53 (UTC) by Billli11)

llvm and llvm-libs is updated again.
both are currently version 19.1.7-1

https://archlinux.org/packages/extra/x86_64/llvm/
https://archlinux.org/packages/extra/x86_64/llvm-libs/
https://archlinux.org/packages/extra/x86_64/clang/

Billli11 commented on 2025-01-12 17:35 (UTC) (edited on 2025-01-12 17:42 (UTC) by Billli11)

llvm and llvm-libs has been updated to 19.1.6-3 in stable repo.
And the PKGBUILD require update to build.

llvm
llvm-libs

rjahanbakhshi commented on 2025-01-08 11:06 (UTC)

@Lone_Wolf, @Cody_Learner

Thank you. I changed directx-headers-git to directx-headers and removed cmake from the makedepends. Built in a clean chroot env and it seems okay. PKGBUILD updated.

Cody_Learner commented on 2025-01-08 07:56 (UTC) (edited on 2025-01-09 20:11 (UTC) by Cody_Learner)

OK it builds for me now with cmake removed and directx-headers-git changed to directx-headers in the makedepends array.

I do get the ==> WARNING: Failed to install built package(s). due to official repo mesa being installed in the chroot, which is in conflict with mesa-git. This also results in the following: 

==> Running checkpkg
error: target not found: mesa-git
==> WARNING: Skipped checkpkg due to missing repo packages

The checkpkg script wouldn't work for an AUR package anyway...

I used the devtools package pkgctl script, with pkgctl build command.

My personal AUR helper https://github.com/Cody-Learner/aurch doesn't have the capability to run on an edited PKGBUILD for clean chroot builds yet, so I'll test it after the PKGBUILD gets updated.

EDIT: 2025-01-09 04:51PM US west coast time

Test clean chroot build was successful on the updated PKGBUILD using my personal AUR helper aurch: https://github.com/Cody-Learner/aurch

Lone_Wolf commented on 2025-01-07 15:42 (UTC)

The only reason I'm aware of for mesa supporting cmake is to determine llvm versions with special files only usable through cmake.Most linux distros (incl archlinux) use llvm-config for that and don't even include the necessary files with llvm.

remove cmake : yes

As for directx-headers/directx-headers-git : those give issues so often that I wonder if removing d3d12 support isn't smarter .

It only seems to be useful on WSL 2 , how many mesa-git users are running wsl2 ?

For now, change the dep to directx-headers.

rjahanbakhshi commented on 2025-01-07 13:15 (UTC)

@Lone_Wolf,

Are you suggesting that the cmake must be removed from the makedepends and Extra/directx-headers should be installed rather than the aur version?

Lone_Wolf commented on 2025-01-07 11:15 (UTC)

I completely missed cmake was in makedepends, no idea when or why it was added. (mesa-minimal-git has never had it) .

The log posted clearly shows the build error has to do with directx-headers. (not the first time).

I tested without cmake and with directx-headers from repos and everything works.

Please verify if that works for you.

Cody_Learner commented on 2025-01-06 22:00 (UTC) (edited on 2025-01-07 01:01 (UTC) by Cody_Learner)

I'm attempting to clean chroot build using both my own AUR helper https://github.com/Cody-Learner/aurch and the devtools pkgctl script.

The same error stops the build process using either method. 

[3145/3449] Linking target src/gallium/targets/dri/libgallium-25.0.0-devel.so
FAILED: src/gallium/targets/dri/libgallium-25.0.0-devel.so

Is this an isolated issue on my end or a problem with the PKGBUILD?

AUR dependency directx-headers-git was prebuilt and installed in the chroot (therefor compromising it) for both build methods.

Here's the complete build output from an aurch clean chroot build: https://pastejustit.com/raw/52fckz63me
Note: Aurch prebuilds and installs all AUR build dependencies in the clean chroot prior to building specified AUR package.

QUOTE:

mesa builds much better when only meson is present and cmake is NOT.
In a clean chroot only needed deps are installed, and cmake is not needed.
If you want to build with makepkg or an aur helper, remove cmake before building .

Is there a reason for this AUR package to not remove cmake from the makedepends array of the PKGBUILD if it's not needed and causing problems?
Possibly move it into the depends or optdepends array?

Removing cmake from the PKGBUILD, the build process still fails on the same error as above.
I did confirm and that the chroot does not have cmake installed after the failure.

Build output using pkgctl with cmake removed from PKGBUILD: https://pastejustit.com/raw/tednmaywzg

Lone_Wolf commented on 2024-12-27 18:07 (UTC)

copied from miyalys log 

Found CMake: /usr/bin/cmake (3.31.3)
Run-time dependency directx-headers found: NO (tried pkgconfig and cmake)
Run-time dependency directx-headers found: YES 1.614.1

mesa builds much better when only meson is present and cmake is NOT.

In a clean chroot only needed deps are installed, and cmake is not needed.

If you want to build with makepkg or an aur helper, remove cmake before building .

1 2 3 4 5 6 .. 133 Next › Last »