The method to reduce what is getting build uses `ninja -t targets' . That option appears to be exclusive to ninja, for now I'm skipping it.
The commands to split clang files do seem to work, unfortunately they complicate the PKGBUILD further.
I'm currently looking into building from snapshots to see if having separate (simple) PKGBUILDs for llvm, clang & spirv-llvm-translator is worth the effort.
Pinned Comments
Lone_Wolf commented on 2022-11-02 11:39 (UTC)
During building you may encounter lots of coredumps, slowing build down or even dramatically reducing the responsiveness of your system.
See https://wiki.archlinux.org/title/Core_dump for solutions/workarounds .
Lone_Wolf commented on 2020-08-22 12:30 (UTC) (edited on 2020-08-22 12:31 (UTC) by Lone_Wolf)
Archlinux currently has 3 llvm git implementations
this package
llvm-git
packages created & maintained by Lordheavy, an arch developer
Lone_Wolf commented on 2019-08-25 12:39 (UTC) (edited on 2021-01-30 21:15 (UTC) by Lone_Wolf)
Why does this package exist ?
Llvm & aur llvm-git are intended to provide a full development environment of llvm/clang suite that can replace eachother completely (aur llvm-git adds some xtra functionality)
llvm-minimal-git is a stripped-down llvm trunk build with these goals :
Some of the things that are stripped out :
Maintainers (and users) should only depend on llvm-miminal-git after verifying it satisfies what they need.
Lone_Wolf commented on 2019-08-21 13:51 (UTC) (edited on 2022-11-02 11:36 (UTC) by Lone_Wolf)
When building this you are likely to encounter test failures.
Those that mention non-x86-64 and/or non-admgpu architectures are unimportant.
To prevent building abortions due to test failures, you can use --nocheck option of makepkg.