Arch Linux User Repository

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 .

Archlinux currently has 3 llvm git implementations

1. this package

   • see other pinned comments for details

2. llvm-git

   • It aims to provide a full llvm/clang compiler environment for development purposes.
   • Supports cross-compiling , bindings for external stuff (python, ocaml etc) , and some things not in extra-llvm.
   • intended to be used with archlinux core,extra & community repos
   • CONFLICTS with extra llvm/clang packages
   • binary versions in chaotic aur unofficial repository

3. packages created & maintained by Lordheavy, an arch developer

   • intended to be used with archlinux testing repos
   • sometimes has problems on systems where testing repos are disabled
   • uses same package structure as llvm/clang in official repos
   • source
   • binary versions in LordHeavys unoffical repo

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 :

• llvm-libs-minimal-git must coexist with stable llvm-libs
• provide what's needed for mesa trunk (it's a hard dependency for mesa-minimal-git and a possible dependeny for mesa-git)
• provide basic llvm/clang compiler functionality on x86-64 architecture

Some of the things that are stripped out :

• cross-compiling support
• bindings for ocaml
• bindings for go
• lld , lldb and polly
• documentation
• examples
• benchmarks

Maintainers (and users) should only depend on llvm-miminal-git after verifying it satisfies what they need.

When building this you are likely to see test failures in terminal output / logs.

The command used for the tests has been changed to continue regardless of failures. Incase you don't want to run the tests you can use --nocheck option of makepkg.

Thank you very much for the explanation @Lone_wolf Maybe pin it in case someone asks the same question? Edit: nevermind you already did it.

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 :

• llvm-libs-minimal-git must coexist with stable llvm-libs
• provide what's needed for mesa trunk (it's a hard dependency for mesa-minimal-git and a possible dependeny for mesa-git)
• provide basic llvm/clang compiler functionality on x86-64 architecture

Some of the things that are stripped out :

• cross-compiling support
• bindings for ocaml
• bindings for go
• lld , lldb and polly
• documentation
• examples
• benchmarks

Maintainers (and users) should only depend on llvm-miminal-git after verifying it satisfies what they need.

This package doesn't provide llvm-git which is the name most packages depends on. Is it expected?

When building this you are likely to see test failures in terminal output / logs.

The command used for the tests has been changed to continue regardless of failures. Incase you don't want to run the tests you can use --nocheck option of makepkg.

@Faalagorn please examine instructions in llvm-git sticky message.

Commenting out just the check() function made it compile after two previous failures for me – also I see that https://aur.archlinux.org/packages/lib32-llvm-minimal-git/ PKGBUILD is different and among some doesn't include that check, although I didn't try compiling it yet (EDIT: it works fine).

EDIT: Alternatively, it works by disabling check via --nocheck or stating BUILDENV=([…] !check […])

@Octobot : clang regresssion tests fail so often I'm tempted to remove them from the check() function. Usually they go away(and are sometimes replaced by others) after a few days when upstream solved them.

@Sinistar llvm-minimal-git gives more warnings then in the past, but other then that I haven't encountered problems with it or mesa-git using llvm-minimal-git & gcc9 . Will test llvm-git in a few days.

Just a heads up, GCC 9.X seems to be messed up. LLVM will compile fine with clang, or GCC 8.X. Also, MESA will compile ok with GCC 8.X. If you use clang to compile LLVM you will also need to use gold as the linker and add clang as a makedepends.

Example:

    -D CMAKE_C_COMPILER=/usr/bin/clang \
    -D CMAKE_CXX_COMPILER=/usr/bin/clang++ \
    -D LLVM_USE_LINKER=gold \

It seems no matter what I do, I am unable to successfully build this or the full llvm-git packages. Both ceaselessly fail during regression testing. In the case of llvm-minimal, the results are as follows:

.../llvm-minimal-git/src/llvm-project/clang-tools-extra/test/modularize/ProblemsCoverage.modularize:3:10: error: CHECK: expected string not found in input CHECK: warning: {{.}}{{[/\]}}Inputs/CoverageProblems/module.modulemap does not account for file: {{.}}{{[/\]}}Inputs/CoverageProblems/Level3A.h

Testing Time: 61.37s Failing Tests (1): Clang Tools :: modularize/ProblemsCoverage.modularize

Expected Passes : 750 Expected Failures : 1 Unsupported Tests : 1 Unexpected Failures: 1 FAILED: tools/clang/tools/extra/test/CMakeFiles/check-clang-tools cd .../llvm-minimal-git/src/_build/tools/clang/tools/extra/test && /usr/bin/python .../llvm-minimal-git/src/_build/./bin/llvm-lit -sv .../llvm-minimal-git/src/_build/tools/clang/tools/extra/test ninja: build stopped: subcommand failed. ==> ERROR: A failure occurred in check(). Aborting...

Depends on your umask (I default to a non-permissive one) and how you build the package.