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.

At the moment is being used local://llvm-config.h instead of simply llvm-config.h

local:// is used when the source file need to be provided by the user (like for Cisco packettracer)

@FabioLolix,

llvm-config.h resides in the root, next to the PKGBUILD file. It will be copied during the build and will be installed into /usr/include/llvm/Config/llvm-config.h

Note that llvm-config.h only includes the correct config file which is either llvm-config-32.h or llvm-config-64.h

Hello, one where should get llvm-config.h?

Build failure confirmed, working on it.

https://bugs.llvm.org/show_bug.cgi?id=49818

@Lone_Wolf Now it works. Thank you very much.

Uploaded corrected version, please try it.

NOTE : this package conflicts with official llvm , llvm-libs , clang, compiler-rt etc.

If you have applications (f.e. blender & qtcreator) that need those you will have to rebuild such applications against this package.

pacman is supposed to show a conflict between llvm-libs and llvm-libs-git before you get to the installation part.

I'm working on it, atm it looks like I messed up reverting lld-removal in the commit on 2020-10-25 . Will upload new version soon.

How do you solve the following file conflicts?

error: failed to commit transaction (conflicting files)

llvm-libs-git: /usr/lib/libLLVM.so exists in filesystem (owned by llvm-libs)

llvm-libs-git: /usr/lib/libLTO.so exists in filesystem (owned by llvm-libs)

llvm-libs-git: /usr/lib/libRemarks.so exists in filesystem (owned by llvm-libs)