I decided to run ninja clang-check to see if it reported something useful and it did.
0/1] Running the Clang regression tests
llvm-lit: /home/panoramix/Documents/Aur/pkgbuilds/llvm-git/src/llvm-project/llvm/utils/lit/lit/llvm/config.py:341: note: using clang: /home/panoramix/Documents/Aur/pkgbuilds/llvm-git/src/_build/bin/clang
llvm-lit: /home/panoramix/Documents/Aur/pkgbuilds/llvm-git/src/llvm-project/llvm/utils/lit/lit/llvm/config.py:203: fatal: Couldn't find the include dir for Clang ('/home/panoramix/Documents/Aur/pkgbuilds/llvm-git/src/_build/bin/clang')
FAILED: tools/clang/test/CMakeFiles/check-clang
Comparing include files between this package, my llvm-lw-* variant and repo llvm shows this package is indeed missing some.
example : extra/compiler-rt & compiler-rt-lw-git both have usr/include/sanitizer/ & /usr/include/xray folders. llvm-git has those folders under usr/lib/clang/9.0.0/include .
It looks like compiler-rt and/or clang are not build correctly. This needs to be investigated further.
Pinned Comments
Lone_Wolf commented on 2021-08-16 11:26 (UTC)
When you have this package installed applications that are built against repo-llvm/clang WILL fail unless they are rebuild against this package.
This includes QTCreator, kdevelop , mesa, intel-compute-runtime, gnome-builder to name a few.
Lone_Wolf commented on 2020-08-22 12:18 (UTC) (edited on 2021-02-06 12:51 (UTC) by Lone_Wolf)
Archlinux currently has 3 llvm git implementations
This package
llvm-minimal-git
packages created & maintained by Lordheavy, an arch developer
Lone_Wolf commented on 2019-04-12 20:41 (UTC) (edited on 2019-12-16 22:45 (UTC) by Lone_Wolf)
I've looked good at clang-trunk , llvm-svn, repo llvm/clang packages and think this package is now on route to become a worthy successor to llvm-svn .
llvm-libs-git holds the runtime libraries.
llvm-git
The Package now uses a new environment variable to make ninja behave, NINJAFLAGS. If you want to use it adjust the snippet below to your desired values and add it to makepkg.conf.
Incase you are satisfied with ninja defaults you don't need to do anything.
The check() function fails rather often, but I do suggest to build with them. If build fails due to test failure you can add --nocheck to skip the tests.