Arch Linux User Repository

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.

Archlinux currently has 3 llvm git implementations

1. This package

   • 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
   • Currently there's no repo with binary versions

2. llvm-minimal-git

   • focuses on providing stuff needed for AUR mesa-git. Doesn't support cross-compiling or any bindings for external stuff like ocaml & python.
   • intended to be used with archlinux core,extra & community repos
   • compatible with extra llvm/clang packages
   • no repo with binary versions

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

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.

  It conflicts with the repo llvm-libs package. This is the only way to make sure the llvm linker from git is used, and that's needed for a full dev environment.

• llvm-git

  has llvm , clang, compiler-rt, ocaml & python bindings, polly , lld , lldb .

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.

# Add to makepkg.conf
# limit ninja to 20 jobs
# requires special code in PKGBUILD
# see ninja --help for additonal options
NINJAFLAGS="-j20"

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.

I assumed lordheavy compiled the llvm git packages from the AUR, instead of making his own PKGBUILD. Shouldn’t there still be conflicting files between llvm-libs and llvm-libs-git? Why does it still install?

Archlinux currently has 3 llvm git implementations

1. This package

   • 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
   • Currently there's no repo with binary versions

2. llvm-minimal-git

   • focuses on providing stuff needed for AUR mesa-git. Doesn't support cross-compiling or any bindings for external stuff like ocaml & python.
   • intended to be used with archlinux core,extra & community repos
   • compatible with extra llvm/clang packages
   • no repo with binary versions

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

@lahwaacz @shoober420 yeah, both the AUR and chaotic-aur versions of llvm-libs-git definitely conflict with llvm-libs:

:: llvm-libs-git and llvm-libs are in conflict. Remove llvm-libs? [y/N]

@shoober420 You're installing a binary package from https://pkgbuild.com/~lcarlier/$repo/$arch which is not necessarily the same as this AUR package. It is a binary package with the same name, but you don't have its PKGBUILD.

pacman.log (https://pastebin.com/npvqy7dK) / pacman.conf (https://pastebin.com/b21pvK3Z)

So llvm-git will conflict with llvm, but llvm-libs will not conflict with llvm-libs-git.

That doesn't make sense.

both llvm-libs-git and llvm-libs have /usr/lib/LLVMgold.so and should give a file conflict upon installing.

llvm-git has a hard dependency on llvm-libs-git which should result in a conflict with llvm-libs also.

Assuming you have llvm-libs-git installed now, try to install llvm-libs and post the terminal output, relevant part of pacman.log and your pacman.conf .

Edit : lib32-llvm-libs-git uses the same logic, for troubleshooting we'll focus on the 64-bit package.

I’m not sure why, but this package does not conflict with the llvm-libs package in the official repository. I’m able to have both installed simultaneously. I’m for certain this is not intended. I have to manually remove llvm-libs.

@ johngalt : looking into it, LLVM_POLLY_LINK_INTO_TOOLS was supposed to be a temp fix anyway.

@ Can221-ParOS

The very best way to avoid ocaml issues is to build in a clean chroot environment, https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_clean_chroot

Failure during tests is rather common for this package, use makepkg --nocheck option to skip them completely.

Do you need the full compiler environment or would https://aur.archlinux.org/packages/llvm-minimal-git/ be enough for your purpose ?