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.

no problems at all except some tests failing (--nocheck solves that).

Ignore what i earlier said about symlinks problems, it was user error.

The PKGBUILDs—here and for lib32—have been updated, and the symlinks should now point correctly to the new shared library. The binary repo has also been updated already. Please let me know if you face any problems with the update.

The name of the shared library has changed,[1] so we need to update our symlinking logic. I'll update the PKGBUILDs accordingly once I'm satisfied with the test builds. The impatient may pick this really simple fix.[2]

1. https://github.com/llvm-mirror/llvm/commit/2a6cf85828509e89e18739e5f4b9a958820d66d4
2. https://github.com/kerberizer/llvm-svn/commit/fce2db1719975169b5ebf9dafd67293eb402336c

Thanks for the notice, @Lone_Wolf! I'll take a look.

Broken symlinks, looks like upstream changed something. r328758 is fine, r328796 is first version in my package cache that has the broken symlink. Building latest version myself has same problem.

$ pacman -Qkk llvm-libs-svn lib32-llvm-libs-svn 
warning: llvm-libs-svn: /usr/lib/libLLVM.so.7.0.0svn-r328858 (No such file or directory)
llvm-libs-svn: 24 total files, 1 altered file
warning: lib32-llvm-libs-svn: /usr/lib32/libLLVM.so.7.0.0svn-r328858 (No such file or directory)
lib32-llvm-libs-svn: 16 total files, 1 altered file
$ 

llvm-libs-svn-7.0.0svn_r328758 :
$ ls usr/lib/libLLVM* -l
lrwxrwxrwx 1 panoramix users       17 29 mrt 06:34 usr/lib/libLLVM-7.0.0svn-r328758.so -> libLLVM-7.0svn.so
-rwxr-xr-x 1 panoramix users 72531072 29 mrt 06:16 usr/lib/libLLVM-7.0svn.so
lrwxrwxrwx 1 panoramix users       17 29 mrt 06:34 usr/lib/libLLVM.so.7.0.0svn-r328758 -> libLLVM-7.0svn.so
$ 

llvm-libs-svn-7.0.0svn_r328796-1-x86_64.pkg.tar.xz
$ ls usr/lib/libLLVM* -l
lrwxrwxrwx 1 panoramix users       17 29 mrt 18:45 usr/lib/libLLVM-7.0.0svn-r328796.so -> libLLVM-7.0svn.so
-rwxr-xr-x 1 panoramix users 72535768 29 mrt 18:26 usr/lib/libLLVM-7svn.so
lrwxrwxrwx 1 panoramix users       17 29 mrt 18:45 usr/lib/libLLVM.so.7.0.0svn-r328796 -> libLLVM-7.0svn.so
$ 

@trougnouf, thanks for the tip about that bug! As for the error, I'm afraid there isn't enough information in what you've pasted. Look above for the actual error that caused the build to fail. Also, it seems like you're trying to build with yaourt or some other AUR helper. This isn't really supported and it's strongly advisable to instead build the packages in a clean chroot (or use the binary repo).

[ 98%] Building CXX object tools/lldb/tools/lldb-mi/CMakeFiles/lldb-mi.dir/MIUtilThreadBaseStd.cpp.o

[100%] Building CXX object tools/lldb/tools/lldb-mi/CMakeFiles/lldb-mi.dir/MIUtilVariant.cpp.o

[100%] Linking CXX executable ../../../../bin/lldb-mi

[100%] Built target lldb-mi

make: *** [Makefile:152: all] Error 2

==> ERROR: A failure occurred in build().

Aborting...

==> ERROR: Makepkg was unable to build llvm-svn.

==> Restart building llvm-svn ? [y/N]

==> ---------------------------------

==>

That was very anticlimactic.

# FIXME: Temporary fix for LLVM bug 35053:

# "error: undefined reference to 'pthread_atfork'"

# Ref: https://bugs.llvm.org/show_bug.cgi?id=35053

# Credit: SolarAquarion @ AUR

Looks like that's been fixed.

@lahwaacz, indeed, compiler bugs can be a very nasty thing. Thank you so much for helping sort out such issues!

@kerberizer, the package builds fine, it's just the test. I've seen it fail the same way couple of months ago when I last built the package, so now I excluded a short-time overlook and made a bug report. It seems that it's been solved overnight ;-)

I'm also dealing with a rather strange error with clang-svn and CUDA 9.0, which appears when compiling a host code with -x cuda. It's pretty hard to reproduce (I haven't isolated it from my project yet) and the error message makes no sense whatsoever, so I wanted to make sure that the compiler is built correctly.