| Git Clone URL: | https://aur.archlinux.org/mesa-minimal-git.git (read-only, click to copy) |
|---|---|
| Package Base: | mesa-minimal-git |
| Description: | an open-source implementation of the OpenGL specification, stripped down git version |
| Upstream URL: | https://www.mesa3d.org |
| Licenses: | MIT AND BSD-3-Clause AND SGI-B-2.0 |
| 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-vdpau, opengl-driver, vulkan-driver, vulkan-intel, vulkan-mesa-layers, vulkan-radeon, vulkan-swrast, vulkan-virtio |
| Submitter: | shoober420 |
| Maintainer: | Lone_Wolf |
| Last Packager: | Lone_Wolf |
| Votes: | 11 |
| Popularity: | 0.019122 |
| First Submitted: | 2020-12-10 00:38 (UTC) |
| Last Updated: | 2024-09-11 18:17 (UTC) |
rusticl now works with radeonsi, make sure to rebuild libclc-minimal-git . Also don't forget to set RUSTICLE_ENABLE .
$ RUSTICL_ENABLE=radeonsi clinfo --list
Platform #0: rusticl
`-- Device #0: AMD Radeon RX 580 Series (polaris10, LLVM 17.0.0, DRM 3.49, 6.2.10-arch1-1)
$
I stay close to archlinux default vars as listed in https://github.com/archlinux/svntogit-packages/blob/packages/pacman/trunk/makepkg.conf . I do replace -march=x86-64 -mtune=generic with -march=native , build with gcc and use ccache .
As for build order : 1.spirv-headers-git 2.spirv-tools-git 3.llvm-minimal-git 4.libclc-minimal-git 5.mesa-minimal-git
If libclc-minimal-git build fails there's a problem with the llvm-minimal-git build .
Hello again, unfortunately I'm still getting the same error, even by following your suggestions or by building llvm-git.
Would you mind sharing your MAKEFLAGS ?
Also now that I'm back on LLVM and Clang 15, what is the actual build order, because in the llvm-minimal-git "!lto" is present, but I think even with that it still build with lto enabled for me for some reason.
Thank you.
Lone_Wolf I thank you so much, for the quick response and the help, also I did not know that "LTOFLAGS" existed so thanks for the tip ! Will rebuild everything with your suggestions.
Nohan, the errors point to a problem in the llvm-minimal-git binaries. You may not have noticed it, but the llvm-minimal-git package explicitly disables lto through the options array in PKGBUILD
I expect your adding of -flto=thin to CFLAGS overrides that. please remove it from CFLAGS.
makepkg.conf has a variable LTOFLAGS="-flto=auto" , you could try to set that to thin instead of auto and verify if that honors the !lto option in the PKGBUILD .
Note that there's a build failure with llvm trunk https://github.com/llvm/llvm-project/commit/b677d0753c0a771c6203607f5dbb56189193a14c and later, so you have to build against an older llvm-minimal-git . follow https://gitlab.freedesktop.org/mesa/mesa/-/issues/8297 to keep track of the issue.
Hi, I'm trying to build this package, but it fails as well as the libclc-minimal-git package when trying to use the linker:
On libclc:
-- The CXX compiler identification is Clang 17.0.0
-- The C compiler identification is Clang 17.0.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - failed
-- Check for working CXX compiler: /usr/bin/clang++
-- Check for working CXX compiler: /usr/bin/clang++ - broken
CMake Error at /usr/share/cmake/Modules/CMakeTestCXXCompiler.cmake:63 (message):
The C++ compiler
"/usr/bin/clang++"
is not able to compile a simple test program.
It fails with the following output:
Change Dir: /home/nohan/.cache/paru/clone/libclc-minimal-git/src/_build/CMakeFiles/CMakeScratch/TryCompile-ZjIESG
Run Build Command(s):/usr/bin/ninja cmTC_3276e && [1/2] Building CXX object CMakeFiles/cmTC_3276e.dir/testCXXCompiler.cxx.o
[2/2] Linking CXX executable cmTC_3276e
FAILED: cmTC_3276e
: && /usr/bin/clang++ -march=native -mtune=native -O3 -pipe -fno-plt -flto=thin -flto -Wl,-O2,--sort-common,--as-needed,-fuse-ld=lld,-z,relro,-z,now,-s -flto CMakeFiles/cmTC_3276e.dir/testCXXCompiler.cxx.o -o cmTC_3276e && :
/usr/bin/ld : erreur fatale : LLVM gold plugin has failed to create LTO module: Unknown attribute kind (86) (Producer: 'LLVM17.0.0' Reader: 'LLVM 15.0.7')
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
ninja: build stopped: subcommand failed.
CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
CMakeLists.txt:3 (project)
And it's the same on mesa
I've built llvm-libs-minimal-git, llvm-minimal-git without any problem and by using the linker aswell. I can turn off lto for libclc so that it can build succesfully, but mesa-minimal-git uses lto by default.
ld -v returns "GNU gold (GNU Binutils 2.40) 1.16"
My makeflags are:
CFLAGS="-march=native -mtune=native -O3 -pipe -fno-plt -flto=thin" CXXFLAGS="$CFLAGS" LDFLAGS="-Wl,-O2,--sort-common,--as-needed,-fuse-ld=gold,-z,relro,-z,now,-s"
And it fails with and without ccache enabled or by using -fuse=lld or -fuse=gold.
Thanks for the alert , xenu .
Locally I have removed the dri-drivers option and will upload a new version soon.
One caveat : there's a build failure in mesa trunk when building against llvm 17 trunk .
I am considering adding rusticl opencl support to this package, possibly removing clover opencl .
Thoughts ?
It works now as of version Mesa 22.3.0_devel.160894.df3fdbdeb50-1 (all previous ones failed with the same error message as pasted into the gist).
Pinned Comments
Lone_Wolf commented on 2023-05-22 12:07 (UTC) (edited on 2024-09-06 21:16 (UTC) by Lone_Wolf)
Build order
N.B. these packages are closely tied together, make sure you build all of them in a short period of time (worst case on my system is around 3 hours) .Build frequency
I aim to build everything (including the lib32 part) atleast once a week.
How often you build this is a personal choice, but once a month is in my opinion the absolute minimum .
In that timeframe mesa will have seen almost 1k commits, llvm/clang gets more.
Lone_Wolf commented on 2021-01-22 18:36 (UTC) (edited on 2021-01-22 18:39 (UTC) by Lone_Wolf)
Why does this package hard depend on llvm-minimal-git ?
performancearchlinux repo packages are build with
-march=x86-64 -mtune=genericwhich works on lots of machines but makes limited use of modern processor capabilities. For many packages this has little impact, but with llvm my experience is different.My local builds for llvm / mesa are done with
-march=nativeand this has a noticeable effect on their performance.How big the benefit of this is depends heavily on the exact hardware you use. Worse, the software setup also impacts this. The only way to find out if it benefits your system/software setup is to try it out yourself.
easier maintenance and troubleshootingSince i started my first mesa trunk package late in 2010 I have maintained versions without any llvm, one llvm implementation, split versions, singular versions, versions supporting multiple llvm implementations , switch from libgl hacks libglvnd to allow mesa & nvidia to cooperate etc.
Depending on one llvm variant in a non-splitted singular version results in a simple PKGBUILD that is easy to maintain.
Troubleshooting is also much easier if maintainer uses the same llvm variant as users.
If people feel those reasons are not good enough to hard depend on llvm-minimal-git , maybe I should transfer ownership .
Lone_Wolf commented on 2021-01-09 15:02 (UTC)
Why does this exist ?
Basically mesa/mesa-git build almost everything they can build.
This package tries to build just enough so everyone can use it, but disables older and/or unused components.
Check https://bbs.archlinux.org/viewtopic.php?id=261629 for a discussion about this package.