Arch Linux User Repository

Build order

llvm-minimal-git
spirv-headers-git
spirv-tools-git
spirv-llvm-translator-minimal-git
libclc-minimal-git
glslang-minimal-git
mesa-minimal-git

glslang-minimal-git must be built after spirv-tools-git and before mesa-minimal-git

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

In that timeframe mesa will have seen almost 1k commits, llvm/clang gets more.

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 .

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.

I had an issue with opengl games freezing after a short time and causing a GPU reset (Radeon 6900XT). Same game run with zink worked fine. Downgrading llvm/clang to version 12 and rebuilding this package resolved the issue. Anyone else run into this?

Depends on which functionality you need.

• libunwind is for debugging

• lmsensors adds graphics related sensors to lmsensors database

• gallium-opencl enables opencl through libclc, but mainly works on polaris (like RX 580) and earlier cards.

If you feel you don't need / want that functionality, you can disable them and simplify dependencies a bit .

Oops! you're right. I cloned that one instead!

Thanks for maintaining this really! Now I want to go more minimal with only AMD stuff, should I only edit the vulkan-drivers and gallium-drivers or are there extra stuff to modify in PKGBUILD as well?

This package has a makedepend on llvm-minimal-git , which conflicts & provides clang, compiler-rt and llvm .

It should refuse to build if any other llvm/clang version is present .

Are you use you were using this package and not https://aur.archlinux.org/packages/mesa-minimal+-git ?

(there's a + in its pkgname)

I think clang should be added to makedepends. I had compilation error without it.

The recently added patch '0002-fix-ac_build_atomic_rmw-with-LLVM-13.patch' can be removed again as it was merged upstream (and results in an error during prepare).

Thank you for instructions, I have added same patch found in llvm bug tracker (proposed by you), to allow me to build.

I've added a patch that does allow building opencl again.

Incase you still want to disable opencl , replace icd with disabled in the line -D gallium-opencl=icd \

how to disable opencl building ?

Building with opencl enabled gives a new build failure , see https://gitlab.freedesktop.org/mesa/mesa/-/issues/4200