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

Lone_Wolf commented on 2018-04-02 10:59 (UTC)

*.la files come from libtool, default on arch linux is to remove them during package creation. check your /etc/makepkg.conf , global options section.

Looking into the wayland-git issue

SolarAquarion commented on 2018-04-02 02:40 (UTC)

wayland-git: /usr/lib/libwayland-egl.la exists in filesystem wayland-git: /usr/lib/libwayland-egl.so exists in filesystem wayland-git: /usr/lib/libwayland-egl.so.1 exists in filesystem wayland-git: /usr/lib/libwayland-egl.so.1.0.0 exists in filesystem wayland-git: /usr/lib/pkgconfig/wayland-egl.pc exists in filesystem Errors occurred, no packages were upgraded.

these exist in "mesa"

SolarAquarion commented on 2018-04-02 02:16 (UTC)

esa-git: /usr/lib/libGLESv1_CM.la exists in filesystem mesa-git: /usr/lib/libGLESv2.la exists in filesystem Errors occurred, no packages were upgraded. ==> WARNING: Failed to install built package(s). ==> Cleaning up... makepkg -rsciC 14.62s user 0.88s system 60% cpu 25.623 total solaraquarion@apollo   ~/build/mesa-git    cb211a7654ba  master    sudo pacman -Qo /usr/lib/libGLESv1_CM.la /usr/lib/libGLESv1_CM.la is owned by libglvnd 1.0.0-1

Lone_Wolf commented on 2018-04-01 09:58 (UTC)

Thanks for the link , jpapadopoulos I had noticed the build failure but not gotten around to looking for solutions. Given it's passover now, it may take a while before the patch lands in master.

Uploaded new version of mesa-git with this patch added. will do lib32-mesa-git soon also.

jpapadopoulos commented on 2018-03-31 11:50 (UTC) (edited on 2018-03-31 11:55 (UTC) by jpapadopoulos)

Mesa needs this patch to build atm. https://patchwork.freedesktop.org/patch/213931/ It seems likely this will be merged soon though

Lone_Wolf commented on 2018-03-15 15:21 (UTC)

I've done some investigating on my own and have removed valgrind as makedep from my libdrm-git packages. mesa-git now again detects libdrm without needing valgrind, so i've removed valgrind also from this package.

haagch commented on 2018-03-14 11:50 (UTC)

Yea this package has not been updated in a long time. I take your word for it that the PKGBUILD works and updated it. I only commented out the debug and !strip options.

corrupt commented on 2018-03-14 11:45 (UTC) (edited on 2018-03-14 11:45 (UTC) by corrupt)

Current pkgbuild does not install json file with driver description (/usr/share/vulkan/icd.d/intel_icd.x86_64.json) and loader cannot find the driver (/usr/lib/libvulkan_intel.so). So vkCreateInstance fails.

This pkgbuild solves the problem: https://pastebin.com/k5rxNt0q

Lone_Wolf commented on 2018-03-13 13:39 (UTC) (edited on 2018-03-13 13:40 (UTC) by Lone_Wolf)

edit out valgrind from pkgbuild, remove from system if necessary. build mesa-git, after it fails check $srcdir/mesa/config.log search for libdrm and you'll see lines similar to the ones at the bottom.

libdrm on archlinux has been build with valgrind support for a long time, but first time this happened was just after libdrm-git was switched from autotools to meson (libdrm upstream have decprecated autotools and will remove it soon).

when building mesa-git against autotools libdrm pre-2.91 mesa-git didn't need valgrind . It could be a change in libdrm 2.91 , or due to differences between meson/ninja & autotools builds. If you want to investigate, i'd start with testing mesa-git against a libdrm 2.91+ build with autotools.

<hr>

configure:24009: checking for libdrm >= 2.4.75

configure:24016: $PKG_CONFIG --exists --print-errors "libdrm >= $LIBDRM_REQUIRED"

Package valgrind was not found in the pkg-config search path.

Perhaps you should add the directory containing `valgrind.pc' to the PKG_CONFIG_PATH environment variable

Package 'valgrind', required by 'libdrm', not found

craftyguy commented on 2018-03-12 16:28 (UTC)

@Lone_Wolf, what did you find that made you conclude valgrind is necessary for building mesa-git? Was the reason Arch-specific or something else? I have no problems building mesa on other distros (e.g. Debian) without valgrind, so I'm curious why it's needed to build on Arch. FWIW, I also wasn't to build on Arch initially, but installing valgrind fixed the libdrm detection problem as you suggested.

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