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.

@psi Thanks. Updated. Not tested.

current lldb-archlinux-python2-config.patch doesn't work anymore. http://codepad.org/2j4yAJkk replaces the patch file with some sed commands.

You can add -DBUILD_SHARED_LIBS=ON to the cmake commands in the PKGBUILD.

When I try to build mesa from git with --enable-opencl i have it warning: configure: error: Could not find llvm shared libraries: Please make sure you have built llvm with the --enable-shared option and that your llvm libraries are installed in /usr/lib If you have installed your llvm libraries to a different directory you can use the --with-llvm-prefix= configure flag to specify this directory. NOTE: Mesa is attempting to use llvm shared libraries because you have passed one of the following options to configure: --with-llvm-shared-libs --enable-opencl If you do not want to build with llvm shared libraries and instead want to use llvm static libraries then remove these options from your configure invocation and reconfigure. In llvm-svn package used configure and there simply add option --enable-shared. But in your package used cmake. How can I add an option --enable-shared in this package?

@mtahmed @kalenz It's working like a charm. Nice work! Cheers, --TDKPS

@kalenz Updated the PKGBUILD. Thanks!

I cleaned a bit the PKGBUILD and now it compiles the latest svn revision instead of the hardcoded one: http://pastie.org/private/ctvoprgdo7xxwi0ziulmq

@kalenz Thanks! Updated the package but did not test (lack of time :( ).

I patched the PKGBUILD to make it work: http://pastie.org/private/d62f9zjjsrijrcrdu58qg And you'll need this patch as well: http://pastie.org/private/6xavfihkw9tjnpsf4xaddw