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.

This is the tools/gold/README: This directory contains a plugin that is designed to work with binutils gold linker. At present time, this is not the default linker in binutils, and the default build of gold does not support plugins. Obtaining binutils: cvs -z 9 -d :pserver:anoncvs@sourceware.org:/cvs/src login {enter "anoncvs" as the password} cvs -z 9 -d :pserver:anoncvs@sourceware.org:/cvs/src co binutils This will create a src/ directory. Make a build/ directory and from there configure binutils with "../src/configure --enable-gold --enable-plugins". Then build binutils with "make all-gold". To build the LLVMgold plugin, configure LLVM with the option --with-binutils-include=/path/to/binutils/src/include/ --enable-pic. To use the plugin, run "ld-new --plugin /path/to/LLVMgold.so". Without PIC libLTO and LLVMgold are not being built (because they would fail link on x86-64 with a relocation error: PIC and non-PIC can't be combined). As an alternative to passing --enable-pic, you can use 'make ENABLE_PIC=1' in your entire LLVM build. How on earth to I edit the PKGBUILD for this?

LLVMgold.so, the linker plugin seems to have disappeared after replacing the repo clang with this; which breaks a number of my builds. How to recover it?

@ aksr lldb also crashes on my VmWare VM, see http://llvm.org/bugs/show_bug.cgi?id=17802 You could check if you have the same backtrace of the crash, either running lldb from gdb or examining the core file with gdb. To disable the handling of core dumps by systemd-coredumpctl(1), see https://wiki.archlinux.org/index.php/Systemd#Disabling_application_crash_dumps_journaling

No, something else is missing. I reinstalled everything, still, the same problem persists.

You could have corrupt llvm libraries. Could you first re-install llvm-libs and then try re-compiling and re-installing this AUR package and let me know?

It seems this version is too old. You could try to build with gcc instead of clang. The new package version does not depend on clang to build lldb anymore. It takes a bit longer but should be possible (I tried it with the repository version yesterday). Another thing you could try would be to remove the lldb part from the PKGBUILD, build and install LLVM+clang and then try the full install which should then benefit from the newly installed clang version.

Version from the official repo: clang version 3.3 (tags/RELEASE_33/final)

Still, it doesn't work. It segfaults if I try to *run* program within it. I'm not sure what could be the problem, since I use compilers (gcc, clang) from the official repositories. I tried to compile other package (which contains lldb), but with no success: https://privatepaste.com/2955f51a7c .

Which version of clang are you using for compilation?

schulmar: I'm unable to compile it. Here's a output snippet: https://privatepaste.com/29de3eb45d I'm using clang from the official repository(extra).