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 .. 54 55 56 57 58 59 60 61 62 63 64 .. 131 Next › Last »

Lone_Wolf commented on 2019-03-21 11:44 (UTC)

same error for me, will have to investigate. I'll be busy today and tomorrow, so won't be able to do that soon.

zfkerr commented on 2019-03-21 11:04 (UTC) (edited on 2019-03-21 11:05 (UTC) by zfkerr)

@Lone_Wolf What I should to do? Compilation error:

Running custom install script '/usr/bin/python /tmp/Mesa-git/src/mesa/bin/install_megadrivers.py /tmp/Mesa-git/src/_build/src/mesa/drivers/dri/libmesa_dri_drivers.so /usr/lib/dri i915_dri.so i965_dri.so radeon_dri.so r200_dri.so nouveau_vieux_dri.so'
Traceback (most recent call last):
  File "/tmp/Mesa-git/src/mesa/bin/install_megadrivers.py", line 74, in <module>
main()
  File "/tmp/Mesa-git/src/mesa/bin/install_megadrivers.py", line 48, in main
shutil.copy(args.megadriver, master)
  File "/usr/lib/python3.7/shutil.py", line 245, in copy
copyfile(src, dst, follow_symlinks=follow_symlinks)
  File "/usr/lib/python3.7/shutil.py", line 121, in copyfile
with open(dst, 'wb') as fdst:
PermissionError: [Errno 13] Permission denied: '/usr/lib/dri/libmesa_dri_drivers.so'
FAILED: meson-install 
/usr/bin/meson install --no-rebuild
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in package_mesa-git().
Aborting...

ltsdw commented on 2019-03-21 01:00 (UTC) (edited on 2019-03-21 01:01 (UTC) by ltsdw)

Getting this, any idea why? I compiled mesa last week, so I don't have any idea why I'm seeing this (also I tried makepkg -C) 


Traceback (most recent call last):
  File "/home/little/.cache/yay/mesa-git/src/mesa/bin/install_megadrivers.py", line 74, in <module>
    main()
  File "/home/little/.cache/yay/mesa-git/src/mesa/bin/install_megadrivers.py", line 48, in main
    shutil.copy(args.megadriver, master)
  File "/usr/lib/python3.7/shutil.py", line 245, in copy
    copyfile(src, dst, follow_symlinks=follow_symlinks)
  File "/usr/lib/python3.7/shutil.py", line 121, in copyfile
    with open(dst, 'wb') as fdst:
PermissionError: [Errno 13] Permission denied: '/usr/lib/dri/libmesa_dri_drivers.so'
FAILED: meson-install 
/usr/bin/meson install --no-rebuild
ninja: build stopped: subcommand failed.
==> ERRO: Uma falha ocorreu em package_mesa-git().
    Abortando...

Lone_Wolf commented on 2019-03-20 10:56 (UTC)

zor1984qq

I use ccache permanently and have no problems.

Not starting in a clean enviornment is a common error cause, try cleaning the srcdir before building ( makepkg -C ) .

Lone_Wolf commented on 2019-03-20 10:51 (UTC) (edited on 2019-03-20 11:00 (UTC) by Lone_Wolf) 

DEPRECATION: Project targetting '>= 0.45' but tried to use feature deprecated since '0.48.0': python3 module

from http://mesonbuild.com/Release-notes-for-0-48-0.html

python3 module is deprecated

A generic module python has been added in Meson 0.46.0 and has a superset of the features implemented by the previous python3 module.

In order to switch from the deprecated python3 to the new python module, mesa would have to increase minimum supported meson version.

Whether that will be done depends on the meson versions used by distros. Personally I'm ok with waiting.

zor1984qq commented on 2019-03-18 10:17 (UTC) (edited on 2019-03-18 10:18 (UTC) by zor1984qq)

Its not compiling, giving me error with ccache. Can ccache in makepkg.conf affect compilation? I used up slightly modified makepkg.conf only with -j2 + ccache enablement. Manjaro latest updated system.

zfkerr commented on 2019-03-17 16:36 (UTC)

@Lone_Wolf, hi! Tell me, please, what does this warning mean? Why do we use deprecated features? Thank you!

WARNING: Deprecated features used:
 * 0.48.0: {'python3 module'}

Haxk20 commented on 2019-03-16 17:48 (UTC)

Bug reported on mesa bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=110141

Haxk20 commented on 2019-03-16 17:36 (UTC)

Yup wait a sec

Lone_Wolf commented on 2019-03-16 13:35 (UTC) (edited on 2019-03-16 13:36 (UTC) by Lone_Wolf)

That helps to understand the issue.

I checked and before b01524fff05eef66e8cd24f1c5aacefed4209f03 mesa-git included

usr/lib/pkgconfig/glesv1_cm.pc usr/lib/pkgconfig/glesv2.pc

After that commit those files are no longer present so pkgconfig is not aware the system has gles support. It's unclear to me whether those files should be provided by mesa or glvnd, but one of them has to.

This is not a mutter bug, but a mesa / glvnd miscommunication. Since mesa changed its behaviour I do think a mesa bug needs to be created. Could you create a mesa bug and post the link here and in the (hopefully) existing mutter bug report ?

« First ‹ Previous 1 .. 54 55 56 57 58 59 60 61 62 63 64 .. 131 Next › Last »