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.

I'm getting a conflict with the resulting llvm-git package and python2-six:

$ pacman --query --list --file -- llvm-git-9.0.0_r314120.c77bf89dcce-1-x86_64.pkg.tar.gz | grep six.py

llvm-git /usr/lib/python2.7/site-packages/six.py

Clang is still borked here... :/

https://invent.kde.org/snippets/153

@Lone_Wolf, thanks!

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.

Well, this is unexpected and a bit awkward.

A few days ago I started my own llvm development packages.

Then llvm-svn was merged into llvm-git, lib32-llvm-svn into lib32-llvm-git . I was already co-maintainer of llvm-git , made co-maintainer of lib32-llvm-git. Yurikoles orphaned those packages and aur server interface promoted me to maintainer .

So now i'm maintainer of 2 sets of llvm dev packages.

I do think there's room for 2 implementations: my personal one in llvm-lw-git and this package as a continuation of llvm-svn that builds everything. It does need several sub-pacakges but they'll stay in the same pkgbuild.

I dislike the non-copyleft nature of llvm license and my personal use of llvm trunk is limited to mesa-git.

I will keep maintainership of this package for atleast a few weeks, but would prefer if someone who actually uses llvm/clang to compile stuff takes over.

Kerberizer : thanks for all the work you put in llvm-svn. please stay involved with it.

Yurikoles : thank you for stepping up and starting this pacakge when llvm-svn was broken.

The pinned comments will stay as-is for now as a sort of tribute.

Lone_Wolf

Is Clang borked for anyone else?

Attempting to run it with this package results in this lovely segfault:

https://invent.kde.org/snippets/133

I have used this package and bearoso' work as well as yurikoles llvm-git to create new packages . I've uploaded the ones needed for mesa-git and will look into others (lld, lldb, polly) later.

You can find them here :

https://aur.archlinux.org/pkgbase/llvm-lw-git/

https://aur.archlinux.org/pkgbase/compiler-rt-lw-git/

https://aur.archlinux.org/pkgbase/clang-lw-git/

https://aur.archlinux.org/pkgbase/lib32-llvm-lw-git/

Please test them and comment.

Please re-enable tests and add a check function .

Incase tests fails, makepkg has a very useful option : --nocheck .

@bearoso, please send I PR https://github.com/yurikoles-aur/llvm-git

@yurikoles You couldn't have done this a day sooner? I gave up waiting and made my own packages yesterday. :-)

Your package doesn't install clangd-indexer, though. In my package I just used sed to replace "add_clang_executable" with "add_clang_tool" in clang-tools-extra/clangd/indexer/CMakeLists.txt.