ln -s /usr/bin/glslang /usr/bin/glslangValidator
may be a slightly safer workaround...
But thanks for providing that fix bio3c, super helpful!
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.47 |
First Submitted: | 2014-06-19 21:33 (UTC) |
Last Updated: | 2024-09-15 20:40 (UTC) |
« First ‹ Previous 1 .. 14 15 16 17 18 19 20 21 22 23 24 .. 131 Next › Last »
ln -s /usr/bin/glslang /usr/bin/glslangValidator
may be a slightly safer workaround...
But thanks for providing that fix bio3c, super helpful!
Program glslangValidator found: NO
mesa/meson.build:556:17: ERROR: Program 'glslangValidator' not found or not executable
Couldn't find this change on meson.build upstream... glslang repo recently changed glslang to glslangValidator, cp /usr/bin/glslang /usr/bin/glslangValidator
builds just fine...
@edtoml, @Lone_Wolf
Not exactly sure what was wrong, but I sent a fix for the 'pkgver' error when building for staging/23.2. I also tested it with the main branch, and the behavior remains unchanged.
@edtoml I've done some more checking and it doesn't look like it is the change in the pkver() function that caused the failure.
branch=staging/23.1 in the sourceurl does work, branch=staging/23.2 fails.
Using commit= with the hashes of the 2 most recent commits of the staging/23.2 branch gives the same result.
I suggest you try to confirm those results.
(as documented)? Thought I read this this was expected somewhere it the comments. In any case a fix would be very much appriecated. TIA
The new pkgver() breaks when not using main (as documented).
It does indeed fail with branch staging/23.2 but I can't pinpoint the cause as it seems to fail upon entering pkgver .
Where can that documentation be found ?
As for adding an extra option for llvm : can be considered when/if someone creates an aur package for it.
From my POV the new pkgver() is a PITA. I have little to no interest in tracking the main git branch. I do however, like to track the staging/2x.y branch or the tagged rcx versions. The new pkgver() breaks when not using main (as documented). It would be VERY nice if there was a commmented out section in pkgver() which we could enable to let tagged or other branches build. I tracked mesa 23.1-rcx version with no noticed llvm issues. That being said, I have a manually built copy of llvm in $HOME/local/llvmxx (see aur zig-git)- it would be nice if there was a fifth option to easily select this llvm.
The pkgver() function used is based on the no tags version for git packages from the VCS guidelines gitpage.
Many users asked for something to easily compare this version with that of the stable version in repos. The only method to get this value in a reliable & reproducible way is to retrieve it directly from the VERSION file .
The patchver part is taken from the official archlinux PKGBUILD for linux.
Keep in mind that the archlinux dev Lord Heavy uses the same pkgver() (except for the patchver part) in his unofficial mesa-git repository , see https://gitlab.com/lordheavy/mesa-git/-/blob/master/mesa-git/PKGBUILD .
The AUR mesa-minimal-git packages and several other mesa trunk packages also use such a pkgver() .
Changing the pkgver() only for mesa-git and lib32-mesa-git would be confusing .
Please implement a proper pkgver()
function as per Arch guidelines.
Thanks for the input , HurricanePootis . If mesa-git only needed to build against repo llvm/clang your patch would work. Unfortunately that's not the case.
Mesa-git package supports building against 4 llvm variants (three of which are llvm trunk versions). Any options used need to work with all of them. I see four changes in your patch and will discuss them below.
adding intel-nullhw: while it seems to be exlusively used for debugging on intel hardware, it is an official vulkan extension and could be added.
enabling intel-clc : supports raytracing with vulkan on some intel hardware. I am not aware of it being enabled in any aur mesa trunk package so it will need to be tested. If you (or others) want to help try building mesa-git with that option enabled against llvm-minimal-git or llvm-git (once those are confirmed to work, building against lordheavy's llvm trunk packages would also help).
opencl-mesa in repos provides 2 things : clover and rusticl .
clover (aka gallium-opencl) build has been broken with llvm trunk (17+) since februari and continues to fail. The bug ticket https://gitlab.freedesktop.org/mesa/mesa/-/issues/8591 hasn't seen recent activity. Until it is solved mesa-git can't re-enable it.
rusticl
quoted from https://docs.mesa3d.org/rusticl.html SPIRV-LLVM-Translator for a libLLVMSPIRVLib.so matching your version of LLVM, i.e. if you’re using LLVM 15 (libLLVM.so.15), then you need a libLLVMSPIRVLib.so.15.1
extra/spirv-llvm-translator is build against repo llvm and doesn't work with llvm trunk. All llvm trunk varaints need their own version of spirv-llvm-tranalator AND libclc build against their specific llvm variant.
currently those packages don't exist for llvm-git. Someone needs to create and maintain them. Once that has been done rusticl will work with all 4 llvm variants supported by this package and can be added.
If anyone wants to give it a try, look at my aur spirv-llvm-translator-minimal-git & libclc-minimal-git packages to get started.
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.
Option A - best one
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.
Option B - 2nd best
Lone_Wolf commented on 2019-07-09 13:43 (UTC) (edited on 2023-04-18 10:41 (UTC) by Lone_Wolf)
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 ?
Lone_Wolf commented on 2018-01-30 14:06 (UTC) (edited on 2023-02-12 11:56 (UTC) by Lone_Wolf)
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 functionalitybuild lib32-mesa-git
run
glxinfo32 -B
to verify basic OpenGL functionality for multilib programs