Arch Linux User Repository

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.

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

• 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.

• 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

I used $NINJAFLAGS="-j8" And the load went to 56 with firefox. I closed firefox and load stabilized at 24 Prior to "lto1-tran" builds, build time on my machine was 8-mins. Now, it is 17-mins. I let the build completes, and I restarted my machine, I am still seeing incomplete renderings of pixelated images such as user icons, taskmanger preview icons and flicking at the Plasma top panel. It looks like a regression.

I restored to before mesa-git upgrade.

└─(11:20:42)──> glxinfo -B ──(Wed,Jan31)─┘ name of display: :1 display: :1 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: AMD (0x1002) Device: AMD Radeon HD 7800 Series (radeonsi, pitcairn, ACO, DRM 3.56, 6.7.2-x64v2-xanmod1) (0x6818) Version: 24.1.0 Accelerated: yes Video memory: 2048MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 4.6 Max compat profile version: 4.6 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 Memory info (GL_ATI_meminfo): VBO free memory - total: 1018 MB, largest block: 1018 MB VBO free aux. memory - total: 7637 MB, largest block: 7637 MB Texture free memory - total: 1018 MB, largest block: 1018 MB Texture free aux. memory - total: 7637 MB, largest block: 7637 MB Renderbuffer free memory - total: 1018 MB, largest block: 1018 MB Renderbuffer free aux. memory - total: 7637 MB, largest block: 7637 MB Memory info (GL_NVX_gpu_memory_info): Dedicated video memory: 2048 MB Total available memory: 9983 MB Currently available dedicated video memory: 1018 MB OpenGL vendor string: AMD OpenGL renderer string: AMD Radeon HD 7800 Series (radeonsi, pitcairn, ACO, DRM 3.56, 6.7.2-x64v2-xanmod1) OpenGL core profile version string: 4.6 (Core Profile) Mesa 24.1.0-devel (git-8ff3a13e4d) OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.1.0-devel (git-8ff3a13e4d) OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 24.1.0-devel (git-8ff3a13e4d) OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

LTO builds do increase buildtime and memory & IO resources used at buildtime in exchange for runtime performance improvements. Also ninja is known to be resource greedy .

options to mitigate the load :

• prepend NINJAFLAGS="-j N -l N" to the build command (replace N with the number of threads you're willing to use for compiling)

• If you have < 32 GiB memory, consider settting TMPDIR to a location on a SSD (preferably one on a different controller). This slows down the build some, but reduces the memory and IO pressure substantially.

I have a 4-core 8-Thread intel CPU, 8 × Intel® Core™ i7-2600K CPU @ 3.40GHz When building mesa, average load tops around 8-9. Another new observation, now building mesa is out of control, average load is going up to 23-24 slowing the build.

https://photos.onedrive.com/share/8967D5A2C9DBD83D!23830?cid=8967D5A2C9DBD83D&resId=8967D5A2C9DBD83D!23830&authkey=!AO67OmTlDqTIA0g&ithint=photo&e=RfcpIa

└─(04:38:14)──> sudo pacman -Fy 1 ↵ ──(Wed,Jan31)─┘ :: Synchronizing package databases... endeavouros 141.9 KiB 500 KiB/s 00:00 100% core-testing 722.4 KiB 1704 KiB/s 00:00 100% core 1060.5 KiB 2.42 MiB/s 00:00 100% extra-testing 1630.3 KiB 3.37 MiB/s 00:00 100% extra 39.1 MiB 36.7 MiB/s 00:01 100% multilib-testing 2.3 KiB 12.4 KiB/s 00:00 100% multilib 209.3 KiB 595 KiB/s 00:00 100%

└─(04:38:20)──> pacman -F libKF5GuiAddons.so.5 ──(Wed,Jan31)─┘ extra/kguiaddons5 5.114.0-1 (kf5) [installed] usr/lib/libKF5GuiAddons.so.5

I will make a full backup and try again to install latest mesa-git

That doesn't look like it's related to mesa-git.

run pacman -Fy with root rights, then pacman -F libKF5GuiAddons.so.5 to see which package that lib belongs to and whether you have it installed.

on archlinux it's in kguiaddons5 which is needed for gwenview, krusader and a few others.

If you don't have any of those you could change sddm to run under wayland instead of X. see https://wiki.archlinux.org/title/SDDM#Running_under_Wayland

I am running EOS/Wayland/KDE Plasma5. Please let me know if I need to pull in the llvm-git.

/usr/bin/startplasma-x11: error while loading shared libraries: libKF5GuiAddons.so.5: cannot open shared object file: No such file or directory

└─(17:35:31)──> yay -Qi llvm ──(Tue,Jan30)─┘ Name : llvm Version : 16.0.6-1 Description : Compiler infrastructure Architecture : x86_64 URL : https://llvm.org/ Licenses : custom:Apache 2.0 with LLVM Exception Groups : None Provides : None Depends On : llvm-libs perl Optional Deps : None Required By : None Optional For : clang Conflicts With : None Replaces : None Installed Size : 102.03 MiB Packager : Evangelos Foutras foutrelis@archlinux.org Build Date : Fri 18 Aug 2023 10:01:30 AM CDT Install Date : Wed 24 Jan 2024 05:54:10 PM CST Install Reason : Installed as a dependency for another package Install Script : No Validated By : Signature

@Beiruty : running archlinux or a variant like manjaro ? Which llvm are you building against ?

Please post error messages from sddm .

@deemon: repo llvm on archlinux & manjaro appear to be on same version atm, 16.0.6 . Does journal show errors ?

Update right now kills Manjaro (sddm crashes with libllvm errors or something). Timeshift helped. I assume the Manjaro repo LLVM is a bit older than Arch and just need to wait a bit for catchup... or might there something else missing?

With Today's update, I got pixilated user icons and task manager's program preview icons. I timeshifted my system to 2-days ago and everything is fine again. How do I report the bug/regression?

@therealmate,

Thanks, it looks like LTO has been working fine for a while now. https://gitlab.freedesktop.org/mesa/mesa/-/issues/6376#note_2247721

I'm enabling it. If there are any issues, I'll revert.