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

Dependencies (53)

Required by (1315)

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 .. 83 84 85 86 87 88 89 90 91 92 93 .. 131 Next › Last »

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/

Lone_Wolf commented on 2015-11-27 14:30 (UTC)

added xvmc to dependencies

Lone_Wolf commented on 2015-11-03 15:42 (UTC)

I've added VirGL support, you'll need kernel 4.4 or later to try it out.

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

[HEADS UP] Users of `llvm-svn`, `mesa-git` and AMD video cards MUST recompile Mesa If ALL of the following are true for you: * you use an AMD video card with open source drivers, * you use `{lib32-,}mesa-git` from AUR, * you use `{lib32-,}llvm-svn` from AUR, * you have upgraded the `{lib32-,}llvm-svn` packages during the last ~24 hours, whether by compiling yourself or from the `llvm-svn` binary repo, then please note that you MUST recompile the Mesa packages (or possibly upgrade again from the `mesa-git` binary repo you use) due to a recent change in the LLVM shared library. If Mesa is not recompiled, with the new llvm-svn packages you'll most likely face errors like this: gbm: Last dlopen error: /usr/lib/xorg/modules/dri/radeonsi_dri.so: undefined symbol: _ZN4llvm21SymbolTableListTraitsINS_11InstructionENS_10BasicBlockEE13addNodeToListEPS1_ Please note that for the AMD open source drivers recompiling Mesa on every LLVM upgrade is a good practice, even though most of the time it might not be strictly necessary.

Lone_Wolf commented on 2015-09-21 10:24 (UTC)

Yurikoles, from pkgbuild : --with-gallium-drivers=r300,r600,radeonsi,nouveau,svga,swrast \ --enable-llvm-shared-libs \ --enable-gallium-llvm \ Basically everything in mesa-git master that uses gallium needs llvm-svn master to work correctly. llvm-svn projects get hundreds of commits every day, which results in llvm releases being out-of-date a few days after they are released ! If you feel building llvm-svn is to much effort (it does take a long time and lots of disk activty) , search for kerberizer unoffical repo in the wiki. It provides new binary builds of llvm-svn & lib32-llvm-svn every 6 hours.

Eriner commented on 2015-09-20 20:51 (UTC)

@yurikoles building mesa-git without the latest llvm build would be silly.

yurikoles commented on 2015-09-20 20:37 (UTC)

Since llvm-3.7.0 is in testing I advise you to consider stating llvm version requirement instead of dependency on llvm-svn.

kerberizer commented on 2015-09-01 20:29 (UTC)

@agm28011997, sorry to hear about your problems. Please see the reply I left you over on the llvm-svn page.

« First ‹ Previous 1 .. 83 84 85 86 87 88 89 90 91 92 93 .. 131 Next › Last »