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 .
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.014968 |
First Submitted: | 2020-12-10 00:38 (UTC) |
Last Updated: | 2024-09-11 18:17 (UTC) |
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).
I am away from my desktop for about a week, can't help until then.
Hi, few days back I've reported issues building lib32-mesa-minimal-git with vdapu enabled, right now I tried to build mesa-minimal-git (clean new system, just build, pulling latest PKGBUILD) and am getting same issue where it complaints that dependency vdpau cannot be found.. I've uploaded the log to a gist, here: https://gist.github.com/27ced989ea9f8362c217df0333e5ae2e
I'd appreciate some help as I am getting even more puzzled now, why it worked ~5 days ago and now suddenly crashes.. I tried building it "the standard" way via makepkg and also using aurutils to build with and without a chroot, the log is from clean chroot freshly build just for this test..
thx for the alert, xenu.
Although The issues that forced me to disable lto build are still open in mesa bugtracker, I don't encounter them anymore.
LTO build is re-enabled, let me know if you get issues.
Commit https://gitlab.freedesktop.org/mesa/mesa/-/commit/8cc766d8f7eac26b7c029a2fac1bdfdba4776c29 removed xvmc which means the line "gallium-xvmc=disabled" has to be removed from PKGBUILD (same with lib32 version). Otherwise there is an "unknown option" error when building.
In https://gitlab.freedesktop.org/mesa/mesa/-/issues/6486 and https://gitlab.freedesktop.org/mesa/mesa/-/issues/6376 problems were reported with rendering text in many application types :
gtk4 , chromium based, qt/kde based .
The cause is not known atm, but disabling lto gets rid of them completely .
lto build disabled.
Added patches to workaround https://gitlab.freedesktop.org/mesa/mesa/-/issues/6333 and https://gitlab.freedesktop.org/mesa/mesa/-/issues/6359
Also re-enabled clover support
libffi has been updated, so llvm-minimal-git needs a rebuild .
After that rebuild has finished you will need to rebuild this pacakge also .
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 ?
performance
archlinux repo packages are build with
-march=x86-64 -mtune=generic
which 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=native
and 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 troubleshooting
Since 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.