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.46
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 .. 65 66 67 68 69 70 71 72 73 74 75 .. 131 Next › Last »

Strunkenbold commented on 2017-12-28 13:32 (UTC)

Due latest Xorg update you need to remove the following line from PKGBUILD --with-dri-driverdir=/usr/lib32/xorg/modules/dri \

Lone_Wolf commented on 2017-12-02 14:59 (UTC)

copied from PKGBUILD : provides=('mesa' 'opencl-mesa' 'vulkan-intel' 'vulkan-radeon' 'libva-mesa-driver' 'mesa-vdpau' 'mesa-libgl' 'vulkan-driver' 'opencl-driver' 'opengl-driver' 'libtxc_dxtn') yes, the libva-mesa-driver is included.

laichiaheng commented on 2017-12-02 13:31 (UTC)

Is the libva-mesa-driver included in mesa-git?

Lone_Wolf commented on 2017-11-26 18:34 (UTC) (edited on 2017-11-26 18:35 (UTC) by Lone_Wolf)

No problems building 17.4.0_devel.98028.068a72fbcb-1 here, against llvm 6.0.0svn_r318994-1 from kerberizer unofficial repo. Please verify if it still fails to build.

blauerhunger commented on 2017-11-25 21:15 (UTC)

When trying to build this package I get ./configure: line 23189: test: : integer expression expected ./configure: line 23195: test: : integer expression expected configure: error: LLVM 3.9.0 or newer is required for radv and makepkg exits. I experience this in a clean chroot (using extra-x86_64-build) and when just using makepkg on my system. I'm using a freshly built llvm-svn from the AUR package.

kerberizer commented on 2017-10-26 21:10 (UTC)

@darky, just build it. It's fairly normal that -git (or -svn, -hg, etc., for that matter) packages in AUR look "outdated". They need updating in AUR only when something in the build itself changes, which doesn't happen too often. Nevertheless, once you actually start building it on you own, the pkgver() function will kick in to fetch the current version from Git, SVN or whatever VCS system is used.

darky commented on 2017-10-26 21:02 (UTC)

@kerberizer, thanks! I think about it before, but version 2.4.81.r2.gce9e3ba6 confused me. I think need to update it, @Lone_Wolf.

kerberizer commented on 2017-10-26 20:13 (UTC)

@darky, you need to use libdrm-git https://aur.archlinux.org/packages/libdrm-git

darky commented on 2017-10-26 20:06 (UTC)

configure: error: Package requirements (libdrm >= 2.4.85 libdrm_amdgpu >= 2.4.85) were not met: Requested 'libdrm >= 2.4.85' but version of libdrm is 2.4.84 Requested 'libdrm_amdgpu >= 2.4.85' but version of libdrm_amdgpu is 2.4.84 Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables AMDGPU_CFLAGS and AMDGPU_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. ==> ERROR: A failure occurred in build(). Aborting...

Lone_Wolf commented on 2017-10-26 11:00 (UTC)

Removed the patch (and also an older one that was no longer needed but didn't cause harm afaics)

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