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

Dependencies (52)

Required by (1334)

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 .. 85 86 87 88 89 90 91 92 93 94 95 .. 134 Next › Last »

kerberizer commented on 2015-12-25 11:09 (UTC)

@drgn: Since you are, obviously, using Clang to compile Mesa instead of the default GCC, you might want to check this LLVM bug... https://llvm.org/bugs/show_bug.cgi?id=19778 ...and the complete patch proposed by Tomasz in this Mesa bug... https://bugs.freedesktop.org/show_bug.cgi?id=89599 This fixes the build, although I'd probably still recommend using GCC, unless you have very good reasons to replace it with Clang.

tmplt commented on 2015-12-24 23:27 (UTC)

Fails to build with https://ptpb.pw/1XXj (fatal error: error in backend: symbol 'x86_64_entry_start' is already defined) Requested files pasted here: /tmp/tmplt/entry-40f391.c: https://ptpb.pw/-PfC /tmp/tmplt/entry-40f391.sh: https://ptpb.pw/vYxi

Lone_Wolf commented on 2015-12-23 15:16 (UTC)

[makedepends] replaced ocl-icd by libcl [depends] libdrm >= 2.4.66 Currently libdrm in [extra] provides 2.4.65 ,use my new https://aur.archlinux.org/packages/libdrm-git/ for now.

Lone_Wolf commented on 2015-12-22 23:21 (UTC)

Latest mesa fails to build with: configure: error: Package requirements (libdrm_nouveau >= 2.4.66) were not met: Requested 'libdrm_nouveau >= 2.4.66' but version of libdrm_nouveau is 2.4.65 As libdrm 2.4.66 hasn't been tagged or released yet, we'd need a libdrm-git package. Unfortunately such a package doesn't exist yet. If you don't need nouveau driver, for now just remove nouveau from 2 lines in PKGBUILD. @ mnovick1988 : understood, i'll look into changing it.

EndlessEden commented on 2015-12-22 22:25 (UTC)

@Lone_Wolf: libopencl, is precisely what im referring to. IE: people wanting to build side-by-side for linking against this or people wanting the AMD implementation are stuck when trying to build this as-is.

Lone_Wolf commented on 2015-12-12 12:37 (UTC) (edited on 2015-12-12 12:38 (UTC) by Lone_Wolf)

The OpenCL ICD loader is supposed to be a platform-agnostic library that provides the means to load device-specific drivers through the OpenCL API. Most OpenCL vendors provide their own implementation of an OpenCL ICD loader, and these should all work with the other vendors' OpenCL implementations. Unfortunately, most vendors do not provide completely up-to-date ICD loaders, and therefore Arch Linux has decided to provide this library from a separate project (ocl-icd) which currently provides a functioning implementation of the current OpenCL API. seee https://wiki.archlinux.org/index.php/GPGPU#OpenCL_ICD_loader_.28libOpenCL.so.29 -------------------- libcl is a virtual package, not a group. ocl-icd is the only official arch package that provides libcl and i tend to prefer "real" dependencies over virtual dependencies. Afaict the only 2 Aur packages that might give a conflict with ocl-icd are intel-opencl-runtime and libopencl . If there are people that want to use mesa-git together with those packages and report problems, i'll look into it.

EndlessEden commented on 2015-12-12 01:45 (UTC) (edited on 2015-12-12 08:14 (UTC) by EndlessEden)

why is ocl-icd a depend? shouldnt it be libcl(group) for people using proprietary CL bindings? ---- Built with libcl as base, worked fine. package_opencl-mesa-git () { pkgdesc="OpenCL support for AMD/ATI Radeon Mesa drivers" depends=('libxfixes' 'libxext' 'libcl' 'libclc' 'nettle' "mesa-git=${pkgver}") optdepends=('opencl-headers: headers necessary for OpenCL development') provides=("opencl-mesa=$(_mesaver)") replaces=('opencl-mesa') conflicts=('opencl-mesa') install -v -m755 -d "${pkgdir}/etc" mv -v "${srcdir}/fakeinstall/etc/OpenCL" "${pkgdir}/etc/" install -v -m755 -d "${pkgdir}/usr/lib/gallium-pipe" mv -v "${srcdir}"/fakeinstall/usr/lib/lib*OpenCL* "${pkgdir}/usr/lib/" mv -v "${srcdir}"/fakeinstall/usr/lib/gallium-pipe/pipe_{r600,radeonsi}.so "${pkgdir}/usr/lib/gallium-pipe/" install -v -m755 -d "${pkgdir}/usr/share/licenses/opencl-mesa-git" install -v -m644 "${srcdir}/LICENSE" "${pkgdir}/usr/share/licenses/opencl-mesa-git/" }

kerberizer commented on 2015-12-10 13:19 (UTC)

The patch that fixes building against the latest llvm-svn has been committed: http://cgit.freedesktop.org/mesa/mesa/commit/?id=b4a03e7f8f4006eb2c5b09a0611fdda153dd8437

kerberizer commented on 2015-12-09 21:41 (UTC)

Please note that building against the latest llvm-svn code (>= r255078) will fail with the following error: llvm/invocation.cpp: In function ‘std::vector<char> {anonymous}::compile_native(const llvm::Module*, const string&, const string&, unsigned int, std::string&)’: llvm/invocation.cpp:664:63: error: no matching function for call to ‘wrap(std::unique_ptr<llvm::Module>)’ LLVMModuleRef debug_mod = wrap(llvm::CloneModule(mod)); A patch is already coming upstream: https://patchwork.freedesktop.org/patch/67475/

« First ‹ Previous 1 .. 85 86 87 88 89 90 91 92 93 94 95 .. 134 Next › Last »