Package Details: llvm-libs-git 18.0.0_r484887.953ae94149f0-1

Git Clone URL: https://aur.archlinux.org/llvm-git.git (read-only, click to copy)
Package Base: llvm-git
Description: runtime libraries for llvm-git
Upstream URL: https://llvm.org/
Keywords: clang git lld lldb llvm polly
Licenses: custom:Apache 2.0 with LLVM Exception
Conflicts: llvm-libs
Provides: aur-llvm-libs-git, llvm-libs
Submitter: yurikoles
Maintainer: rjahanbakhshi
Last Packager: rjahanbakhshi
Votes: 118
Popularity: 0.006423
First Submitted: 2018-12-05 13:56 (UTC)
Last Updated: 2024-04-17 08:17 (UTC)

Required by (128)

Sources (2)

Pinned Comments

Lone_Wolf commented on 2021-08-16 11:26 (UTC)

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.

Lone_Wolf commented on 2020-08-22 12:18 (UTC) (edited on 2021-02-06 12:51 (UTC) by Lone_Wolf)

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

Lone_Wolf commented on 2019-04-12 20:41 (UTC) (edited on 2019-12-16 22:45 (UTC) by Lone_Wolf)

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.

Latest Comments

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 70 Next › Last »

Lone_Wolf commented on 2021-02-16 18:52 (UTC)

pacman is supposed to show a conflict between llvm-libs and llvm-libs-git before you get to the installation part.

I'm working on it, atm it looks like I messed up reverting lld-removal in the commit on 2020-10-25 . Will upload new version soon.

feng commented on 2021-02-16 15:53 (UTC) (edited on 2021-02-16 15:54 (UTC) by feng)

How do you solve the following file conflicts?

error: failed to commit transaction (conflicting files)

llvm-libs-git: /usr/lib/libLLVM.so exists in filesystem (owned by llvm-libs)

llvm-libs-git: /usr/lib/libLTO.so exists in filesystem (owned by llvm-libs)

llvm-libs-git: /usr/lib/libRemarks.so exists in filesystem (owned by llvm-libs)

Lone_Wolf commented on 2021-01-30 20:18 (UTC)

Thanks for the alert, Sinistar.

Sinistar commented on 2021-01-29 01:59 (UTC)

With LLVM being bumped to 13, "master" has been deleted and "main" added. The HEAD file in your local git will need to be changed to "main", at least for now.

Lone_Wolf commented on 2021-01-22 15:04 (UTC)

Added 2 new make dependencies to solve build failure.

One of them, https://aur.archlinux.org/packages/python-sphinx-automodapi/ is an aur package.

Lone_Wolf commented on 2020-12-06 14:05 (UTC)

Updated PKGBUILD for python 3.9 .

Sinistar commented on 2020-12-03 03:47 (UTC)

FYI Python now at 3.9

Lone_Wolf commented on 2020-10-25 11:18 (UTC)

Tested and I found no trace of the 'llvm adds projects just because their code is in certain locations' that forced me to remove sourcecode folders.

prepare() no longer removes spourcecode folders and lld is back where it should be.

For now I haven't put back llvmgold.so . This means you can have extra llvm-libs and llvm-libs-git installed together.

LLVMgold.so doesn't appear to b eused by many, are there users who can't use repo LLVMgold.so and require the git version of llvmgold.so ?

Lone_Wolf commented on 2020-10-24 18:25 (UTC)

The error is with building the mach-o target, so doesn't occur when only building X86 & AMDGPU targets. llvm-minimal-git doesn't have this problem also.

Leaving the directories intact does indeed allow build to finish. Unfortunately that leads to llvm building a lot more then the projects specifically named (which is exactly the reason why I started deleting those folders).

Maybe llvm devs changed the build process so it doesn't do that anymore , I'll do some test runs.