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

Dependencies (53)

Required by (1302)

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 .. 62 63 64 65 66 67 68 69 70 71 72 .. 131 Next › Last »

yans commented on 2018-04-24 13:26 (UTC)

Lone_Wolf Hi,

I really appreciate your hard work, to create this package. Unfortunately i have some problems after building (CLEAN CHROOT) mesa-git and rest of it. As you said before, wayland-git is needed now. After installing all of it, i have few problems launching for example "firefox" - [yans@corsair ~] $ firefox XPCOMGlueLoad error for file /usr/lib/firefox/libmozgtk.so: libwayland-egl.so.1: cannot open shared object file: No such file or directory Couldn't load XPCOM.

Could you explain what im doing wrong?

Lone_Wolf commented on 2018-04-24 13:06 (UTC) (edited on 2018-04-24 13:07 (UTC) by Lone_Wolf)

  • @zfkerr : python2-mako is a dependency, can mesa now use the python 3 version of mako ? Will look into it.

  • @C0rn3j I checked and the error maybe due to a change in llvm. My last working builds were against 7.0.0svn_r330562-1 . Building against 7.0.0svn_r330683-1 does give me the same error as you.

C0rn3j commented on 2018-04-24 06:38 (UTC)

llvm-svn 7.0.0svn_r330650-1 llvm-libs-svn 7.0.0svn_r330650-1 clang-svn 7.0.0svn_r330650-1

They are and they're the same.

That'd mean my tmpfs would be 16GB, which should be enough, but I tried compiling in ~ just in case and it still didn't help. Ended up on the same errors.

Lone_Wolf commented on 2018-04-23 22:07 (UTC) (edited on 2018-04-23 22:08 (UTC) by Lone_Wolf)

Looking at the log snippet, two possibilities come to mind :

  • you're building in /tmp, which normally is a tmpfs that uses max half your available memory. It seems possible this is to small. Try building on ssd/hdd in some folder under your user home ( like ~/aurbuild ).

  • mesa-git needs llvm-svn, llvm-libs-svn and clang-svn . all 3 need to be of the same version. Are they on your system ?

C0rn3j commented on 2018-04-23 19:50 (UTC)

I've tried to follow the instructions "run pacman -Syu , build & update llvm-svn & lib32-llvm-svn build & update mesa-git build & update lib32-mesa-git"

But I keep getting this error when I get to mesa-git. Any ideas what I'm doing wrong?

https://haste.c0rn3j.com/raw/iyibidonus

Lone_Wolf commented on 2018-04-22 21:56 (UTC)

thank you, patch removed.

mradermaxlol commented on 2018-04-22 18:56 (UTC)

@Lone_Wolf the latest patch you've included breaks the build now - it got upstreamed 3 hours after the package update here :) https://cgit.freedesktop.org/mesa/mesa/commit/?id=f8c4716854ca76c49e5b83fdbe36993deba37908

Lone_Wolf commented on 2018-04-04 12:42 (UTC) (edited on 2018-04-04 12:42 (UTC) by Lone_Wolf)

thx, mradermaxlol. patch for llvm issue removed, now compatible with wayland-git .

NOTE package now conflicts with wayland < 1.14.93 , as earlier wayland versions don't provide wayland_egl .

For now that means you'll have to install wayland-git .

mradermaxlol commented on 2018-04-03 12:14 (UTC)

The patch to address the LLVM issue is not needed anymore: https://cgit.freedesktop.org/mesa/mesa/commit/?id=7e144ace95bc0727301c02ff19f5aa278277f133

« First ‹ Previous 1 .. 62 63 64 65 66 67 68 69 70 71 72 .. 131 Next › Last »