| Git Clone URL: | https://aur.archlinux.org/mesa-minimal-git.git (read-only, click to copy) |
|---|---|
| Package Base: | mesa-minimal-git |
| Description: | OpenCL support in rust for mesa drivers (git version) |
| Upstream URL: | https://www.mesa3d.org |
| Licenses: | MIT AND BSD-3-Clause AND SGI-B-2.0 |
| Conflicts: | opencl-clover-mesa, opencl-rusticl-mesa |
| Provides: | opencl-driver, opencl-rusticl-mesa |
| Submitter: | shoober420 |
| Maintainer: | Lone_Wolf |
| Last Packager: | Lone_Wolf |
| Votes: | 11 |
| Popularity: | 0.010175 |
| First Submitted: | 2020-12-10 00:38 (UTC) |
| Last Updated: | 2024-09-11 18:17 (UTC) |
The build failure was caused by this llvm commit: https://github.com/llvm/llvm-project/commit/ccb2b011e577e861254f61df9c59494e9e122b38
It was reverted with https://github.com/llvm/llvm-project/commit/a15de177728ec83f37bdd8f39d4a8f57e95c3d21 due to build failures
I did a full rebuild without issues.
Built today. Only tested DOOM Eternal and seems to be fine. Only did radeonsi/amd,swrast. Mesa-minimal-git compiled but had trouble moving opencl files to build the package. Removed all opencl related from the PKGBUILD. Built just fine afterwards.
build is broken：
/usr/include/llvm/Support/float128.h:18:18: error: use of undeclared identifier 'logf128'
panicked at bindgen-cli/main.rs:52:36:
Unable to generate bindings: ClangDiagnostic("/usr/include/llvm/Support/float128.h:18:18: error: use of undeclared identifier 'logf128'\n")
EDIT: both are solved now.
There are currently 2 issues with mesa trunk .
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30257 (fix is being worked on)
https://gitlab.freedesktop.org/mesa/mesa/-/issues/11546 is a bigger problem as the commit that causes that is reported as causing atleast one other problem.
pkgver -24.2.0_devel.192122.3de62b2f9a6-1 is the last good one .
I suggest you don't rebuild mesa-minimal-git for now or pin your version to commit 3de62b2f9a6 .
patch applied to solve the build failure
Build is currentyl broken, see https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25265#note_2417849
A change in llvm trunk broke building intel drivers (again) .
Confirming successful compilation with -fpermissive, obviously had to use it to compile 32mesa too as it was failing around line 779 without it. Both mesa-minimal-git and lib32-mesa-minimal-git compiled.
PS, just for the lols compiled mesa with LTO. I see why we have it disabled. Massive graphical issues.
Nope, -fpermissive needs to be used in build() of the mesa-minimal-git PKGBUILD.
No changes are needed in the llvm-minimal-git package.
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.