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.

[HEADS UP] Manual intervention required: version scheme change The new PKGBUILD that I'll be pushing shortly uses a different version scheme. Instead of only the SVN revision number, it also includes the LLVM version number itself. For example, instead of version 241875-1, the new package will have version 3.8.0svn_r244189-1. This is meant to not only help users easier determine what LLVM version they are using, but also to be as close to the output of `llvm-config --version` as possible. However, because of how Pacman treats version numbers, it and likely all AUR helpers that you may be using (e.g. Yaourt) will recognize the new version as a _downgrade_. YOU WILL NEED TO ACCEPT OR FORCE THIS "DOWNGRADE". This will happen only once; all subsequent upgrades should proceed as expected. Sorry for this inconvenience. Technically, it would've been possible to avoid the issue altogether by using the "epoch" variable, but I feel the case doesn't call for such radical measures. Please note as well that the new version will build the Ocaml bindings by default.

Guys, since @Krejzi has stepped down as a maintainer (once again many thanks for all his work on this!), I might try to take his place. However, if there are more knowledgeable and experienced in LLVM and AUR people around, who would be willing to step in, that will certainly be a better choice. If you feel like it, please don't hesitate to raise your hand. ;) If no one else volunteers, I'll take over, at least temporarily, this and the lib32- package, though I won't be able to fix the latter immediately. Meanwhile, I'd like to ask once again everyone to test the PKGBUILD on Github (the link is in my previous comment below). Although I think I've managed to fix the most blatant bugs (i.e. Mesa not building), I'm pretty sure there might be others as well. Any comments and suggestions will be more than welcome.

Guys, @Krejzi, I've made a modified PKGBUILD that uses cmake instead of autotools, since this, from what I could gather, is the preferred method of building LLVM/Clang nowadays. That way, the out-of-source build error is also solved. https://github.com/kerberizer/llvm-svn The PKGBUILD definitely needs more refinement and efficiency improvements and might even have an error or two (e.g. placing some files in wrong places), but at least it seems to work well enough. Feel free to test it; any comments and suggestions will be more than welcome. @Krejzi, if you think it might be helpful, feel free to merge it back here. Speaking of which, I really appreciate your and that of the other contributors work. Thank you!

There was a big update with Mesa and OpenGL 4 recently, you might want to update the regular AUR version of this package.

Should be fixed now.

This package now requires out-of-source build configure: error: In-source builds are not allowed. Please configure from a separate build directory!

Added zrax as a co-maintainer and updated the keywords. zrax: Feel free to update the package is necessary from now on.

Updated the package with pull request from zrax: https://github.com/mtahmed/aur/pull/5

My sincere apologies, I was posting on the wrong package page and also flagged it as out-of-date wrongly. Please disregard and remove the flag.