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.

lordheavy posted a link to the necessary patch if building with gcc. I don't maintain lib32-llvm-svn so there is nothing I can do about it.

Yes, that's also been my first try, but it fails at compile time with: llvm::cl::parser<llvm::PassInfo const*>::getOption(unsigned int) const' which is the error posted by shosca. Somehow, you've made a change to use clang on the 19th, and that did it for the compilation. It seem that lib32-llvm-svn is still suffering of the same issue. I don't mind modifying the PKGBUILD before compiling, I would just like to know what changes you've made, since llvm-svn just compile without errors now, but lib32-llvm-svn still has this error.

There is lib32-llvm-svn if that's what you are looking for

Is there a way to get a lib32-* equivalent of the packages produced by llvm. I run Wine in 32 bit environment for some application (okay... games) and it's a required.

@lordheavy the patch fixes the build

@Krejzi A fix is proposed on the ML about the breakage: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20140616/222509.html

I have uploaded new, real split package PKGBUILD that provides clang-svn too. It now requires clang at build time and package will be built using clang until gcc in [extra] is capable of doing the same again.

Getting the same error as shosca.