Arch Linux User Repository

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
   • binary versions in chaotic aur unofficial repository

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
   • binary versions in chaotic aur unofficial repository

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 don’t see llvm-libs-svn in the AUR anywhere. Even if it did exist in 2015, it doesn’t make any sense to me to leave it in there. So lordheavy’s version of llvm-libs-git is meant to allow multiple installations? I see, well that’s kind of wacky. That explains everything then. He could at least gave it a different name to avoid confusion like you do with your “minimal” package. I’m just going to use official llvm builds and keep it simple.

• Guess I should have clarified what I meant with package structure

  • llvm/clang from repo has
    • llvm
    • llvm-libs
    • llvm-ocaml
    • clang
    • compiler-rt
  • AUR llvm-git has
    • llvm-git
    • llvm-libs-git
    • llvm-ocaml-git
    • does provide clang-git, compiler-rt-git, lld-git, lldb-git and polly-git in llvm-git
  • LH llvm-git has
    • llvm-git
    • llvm-libs-git
    • llvm-ocaml-git
    • clang-git
    • compiler-rt-git

• To get in touch with Lordheavy about things related to his mesa-git repo, try posting in https://bbs.archlinux.org/viewtopic.php?id=212819 .

• LordHeavy introduced llvm-libs specfically to allow multiple llvm versions to coexist.

  • Most parts from llvm needed at runtime are versioned, but the linker LLVMgold.so isn't .
  • Lordheavy llvm-libs-git doesn't include the git version of the linker, aur llvm-libs-git DOES.
  • Kerberizer who maintained llvm-svn for years always felt that an llvm/clang vcs version should provide a full environment including the linker and I have stuck to that.

Aur llvm-libs-svn has conflicted with llvm-libs since (atleast) 2nd half of 2015 and aur llvm-libs-git continues that. LH llvm-libs-git and llvm-libs-svn before that never conflicted with llvm-libs.

The package structure differs enough between the official llvm package and lordheavy’s, mainly being that the official PKGBUILD (https://github.com/archlinux/svntogit-packages/blob/packages/llvm/trunk/PKGBUILD) doesn’t include a provides= and conflicts= section. It shouldn’t anyway since it’s an official repo package, most official repo packages don’t include these sections (harfbuzz and freetype2 are the only that come to mind) Anyway, saying they are the same structure is a stretch, considering “llvm-libs-svn” isn’t even a thing.

Shouldn’t lordheavy’s PKGBUILD conflict “llvm-libs” instead of “llvm-libs-svn”? There isn’t even an svn version in the repos...

I did email lordheavy a while back, and got no response, which led me to believe he was just compiling using your PKGBUILD.

I assumed lordheavy compiled the llvm git packages from the AUR, instead of making his own PKGBUILD. Shouldn’t there still be conflicting files between llvm-libs and llvm-libs-git? Why does it still install?

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
   • binary versions in chaotic aur unofficial repository

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
   • binary versions in chaotic aur unofficial repository

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

@lahwaacz @shoober420 yeah, both the AUR and chaotic-aur versions of llvm-libs-git definitely conflict with llvm-libs:

:: llvm-libs-git and llvm-libs are in conflict. Remove llvm-libs? [y/N]

@shoober420 You're installing a binary package from https://pkgbuild.com/~lcarlier/$repo/$arch which is not necessarily the same as this AUR package. It is a binary package with the same name, but you don't have its PKGBUILD.

pacman.log (https://pastebin.com/npvqy7dK) / pacman.conf (https://pastebin.com/b21pvK3Z)

So llvm-git will conflict with llvm, but llvm-libs will not conflict with llvm-libs-git.