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

Required by (1336)

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

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 .

KrzychuKropopek commented on 2024-12-27 11:34 (UTC)

I'm also installing thru paru, despite directx-headers-git being installed, it still breaks with the same error.

miyalys commented on 2024-12-27 11:16 (UTC) (edited on 2024-12-27 11:17 (UTC) by miyalys)

Personally I was simply trying to install it via an AUR helper - specifically paru.
This is the version of directx-headers-git it installed:
r234.b172a9c-1

Maybe it's because it doesn't build inside a clean chroot, then, and therefore it has the wrong llvm-version...?
I should probably just have read the pinned comments.

rjahanbakhshi commented on 2024-12-27 00:07 (UTC)

@miyalys, @KrzychuKropopek,

25.0.0_devel.199466.c0e5e8f932a.d41d8cd-1 builds ok in a clean chroot environment. Are you building against the latest directx-headers-git? What is the command you use to build?

KrzychuKropopek commented on 2024-12-26 00:50 (UTC)

have the same problem as miyalys

miyalys commented on 2024-12-25 14:55 (UTC) (edited on 2024-12-25 15:33 (UTC) by miyalys)

Getting an error building it - specifically "gallium":

/usr/bin/ld: src/gallium/drivers/d3d12/libd3d12.a.p/d3d12_dxcore_screen.cpp.o: in function `int IDXCoreAdapterFactory::CreateAdapterList<IDXCoreAdapterList>(unsigned int, _GUID const*, IDXCoreAdapterList**)':
/usr/include/directx/dxcore_interface.h:435:(.text._ZL24d3d12_init_dxcore_screenP12d3d12_screen+0xc9): undefined reference to `DXCORE_ADAPTER_ATTRIBUTE_D3D12_GRAPHICS'
/usr/bin/ld: src/gallium/drivers/d3d12/libd3d12.a.p/d3d12_screen.cpp.o: in function `get_debug_interface(util_dl_library*, ID3D12DeviceFactory*)':
/home/m/.cache/paru/clone/mesa-git/src/_build/../mesa/src/gallium/drivers/d3d12/d3d12_screen.cpp:902:(.text._ZL19get_debug_interfaceP15util_dl_libraryP19ID3D12DeviceFactory+0x31): undefined reference to `CLSID_D3D12Debug'
/usr/bin/ld: src/gallium/drivers/d3d12/libd3d12.a.p/d3d12_screen.cpp.o: in function `d3d12_init_screen(d3d12_screen*, IUnknown*)':
/home/m/.cache/paru/clone/mesa-git/src/_build/../mesa/src/gallium/drivers/d3d12/d3d12_screen.cpp:1576:(.text._Z17d3d12_init_screenP12d3d12_screenP8IUnknown+0x63f): undefined reference to `CLSID_D3D12DeviceFactory'
collect2: error: ld returned 1 exit status
[3251/3447] Compiling Rust source src/nouveau/headers/lib.rs
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'mesa-git-24.3.0_devel.194818.d3429a7e00d.d41d8cd-1': 
error: packages failed to build: mesa-git-24.3.0_devel.194818.d3429a7e00d.d41d8cd-1

Not sure if it's a missing build dependency or something.

Full log: https://pastejustit.com/ubfazed8by

LLVM version, installed via pacman: 18.1.8-5

Lone_Wolf commented on 2024-12-09 09:48 (UTC) (edited on 2024-12-09 09:53 (UTC) by Lone_Wolf)

mesa-git-25.0.0_devel.198878.81d0c24e2f6.d41d8cd-1-x86_64.pkg.tar.zst builds fine against repo llvm in a clean chroot build.

What is the llvm variant & version you build against ?

What is the exact command you use to build ?

Please post the full build log somewhere public.

SpiteFire04 commented on 2024-12-08 00:20 (UTC) (edited on 2024-12-08 00:21 (UTC) by SpiteFire04)

"3136/3442] Compiling Rust source src/nouveau/headers/lib.rs ninja: build stopped: subcommand failed. ==> ERROR: A failure occurred in build(). Aborting..."

I keep getting hit with this error

Lone_Wolf commented on 2024-11-30 09:48 (UTC) (edited on 2024-11-30 09:49 (UTC) by Lone_Wolf)

Does CachyOS use pkgconf ?

If so, there's probably a cleaner solution by setting PKG_CONFIG to the correct profile (provided by gcc)

See lib32-mesa-git build() function for an example .

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