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.

Please extract "trunk" to variable "branch". It may be for example "branches/release_37" or "tags/RELEASE_370/final". I have tested all 3 values.

[HEADS UP] Rebuild required I've committed the change that should fix the shared library breakage. This might require some action on your side, namely: * If you build the packages yourself and have last rebuilt them more recently than 08:30 AM UTC yesterday, Sept 5th, please do rebuild them again now. * If you use the binary repo and have last updated your packages from the repo more recently than 09:00 AM UTC yesterday, Sept 5th, please wait until about 11:45 AM UTC today, Sept 6th (half an hour from now; the new packages are still being built), and update again. As usual, please let me know if you find any problems, and especially if they are of the "undefined reference" type when linking to libLLVM, please report them here: https://github.com/kerberizer/llvm-svn/issues/2

For those curious enough, this is the commit that breaks our build, due to the changes to tools/llvm-shlib/CMakeLists.txt, which we parse in order to determine which components we want exported from the shared lib (and which, in turn, we make because of the bug in exporting the necessary symbols on Linux). https://github.com/llvm-mirror/llvm/commit/f5148ebe0ac2e89cf991b7d6e01778bbb8d55034 I'm testing at the moment a changed PKGBUILD that should hopefully produce a working shared lib again. Sorry for any inconvenience.

[WARNING] The shared library seems broken at the moment, with many symbols not being exported. I'm looking into this.

[NOTICE] Possible instability ahead Guys, please take note that in the next days I'll be working on a probably major rework of the PKGBUILD. The reason is that the critical bug with LLVM not exporting the expected symbols has (likely) been fixed upstream at last. This means that the bunch of "awk-ward" dirty tricks currently in the PKGBUILD is probably not needed any more, but I'll have to test this thoroughly. I'll try to make sure that the PKGBUILD stays stable, but just be warned in advance. I'll also post the usual "heads up" once any such changes get committed here. References: * https://github.com/kerberizer/llvm-svn/issues/2 * https://llvm.org/bugs/show_bug.cgi?id=24157 * https://github.com/llvm-mirror/llvm/commit/10add60748226d67d3a1e4d1a8175f798a053708

@Eriner, not sure if that could've been the case here, but sometimes various transient build errors happen just because that's the master branch, with all development constantly going on, and, though rarely, commits do happen to break things, even that badly. They are also usually fixed very quickly, so just waiting an hour or so and building again from fresh source code is all that is needed.

Ah, after completely removing the svn repo and rebuilding it seems to have fixed itself. So if anyone gets the same error as below, remove your llvm-svn folder, git pull, rebuild.

Anyone getting errors like this? https://gist.github.com/Eriner/30274ab4da191d06724c

[NOTICE] The patch to detect incompatible OCaml bindings has just been commited... https://aur.archlinux.org/cgit/aur.git/commit/?h=llvm-svn&id=62e08fbe60743ed35f8e3d34f18644be58d90f25

@agm28011997, I'm glad that you've solved the problems with LLVM and Mesa, and sorry that I cannot offer any advice on Supertuxkart, since I've never played that game. The best place to ask for further help might be the Arch forums... https://bbs.archlinux.org/viewforum.php?id=32 ...and the forum of the game itself... http://forum.freegamedev.net/viewforum.php?f=16