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.009271
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 .. 39 40 41 42 43 44 45 46 47 48 49 .. 70 Next › Last »

kerberizer commented on 2016-02-27 05:38 (UTC)

[NOTICE] There seems to be some problem with lto.h being present in several of the packages simultaneously. I'll look into it later today.

FadeMind commented on 2016-02-24 17:19 (UTC)

@kerberizer. Thanks for quick reply. In future I will post suggestions in main thread. Regards

kerberizer commented on 2016-02-24 16:32 (UTC)

@FadeMind, the out-of-date flag is for flagging the package out of date, not for suggestions. Anyway, I've already explained why I'm very reluctant to switch the svn URLs to https: the SSL/TLS configuration on llvm.org is __bad__. The Qualys SSL test suite rates the site with the worst possible grade, F. This hasn't changed, and the problems are not only critical, but numerous as well. https://www.ssllabs.com/ssltest/analyze.html?d=llvm.org It's probably a good idea to open a ticket on LLVM's issue tracker for this problem, but I don't know if they'd be willing or have the time to fix it.

kerberizer commented on 2016-02-16 18:16 (UTC)

[HEADS UP] Users of "{lib32-,}llvm-svn", "{lib32-,}mesa-git" and AMD video cards MUST recompile Mesa If __all__ of the following are true for you... * you use an AMD video card with the open source drivers, * you use "{lib32-,}mesa-git" from AUR, with version < g0bba5ca, * you use "{lib32-,}llvm-svn" from AUR, with version >= r260919, ...then you __must__ recompile the Mesa packages (or possibly upgrade again from the "mesa-git" binary repo you use). The reason is explained in this Mesa commit: https://cgit.freedesktop.org/mesa/mesa/commit/?id=0bba5ca468cdcd1f6f9bb6736c8a75e43fbe0cd5 If Mesa is not recompiled, you'll face errors of the type: libGL: dlopen /usr/lib/xorg/modules/dri/radeonsi_dri.so failed (/usr/lib/xorg/modules/dri/radeonsi_dri.so: undefined symbol: LLVMAddTargetData) Please note that with the AMD open source drivers, recompiling Mesa on every LLVM upgrade is generally a good practice, even though most of the time it will not be strictly necessary.

chrbayer commented on 2016-02-16 13:32 (UTC)

@kerberizer, looks like no one has missed this so far... I agree it would be best to fill in a bug report upstream. If you would do it, it would be fine for me! Maybe you are more experienced in filling this bug report, but of course I do not want you to lose time... Thank you very much!

kerberizer commented on 2016-02-16 13:22 (UTC)

@chrbayer, from what I can tell, the BlocksRuntime is missing the required CMake configuration: there isn't a CMakeLists.txt in its own directory... https://github.com/llvm-mirror/compiler-rt/tree/master/lib/BlocksRuntime ...and there's no provision for it in the parent CMakeLists.txt too... https://github.com/llvm-mirror/compiler-rt/blob/master/lib/CMakeLists.txt It _is_ referred to in the test suite CMakeLists.txt, so obviously hasn't been entirely forgotten during the transition from autotools... https://github.com/llvm-mirror/compiler-rt/blob/master/test/CMakeLists.txt ...but even there it is commented out, albeit (apparently) for different reasons. I suppose I could try fixing this on my own, but the best way -- if I'm not mistaken in my observations, of course -- would probably be to file a bug report in the LLVM issue tracker. Should I do it or would you do it instead?

chrbayer commented on 2016-02-16 08:56 (UTC) (edited on 2016-02-16 11:19 (UTC) by chrbayer)

I am looking for the BlocksRuntime but it does not seem to be included in the compiler-rt-svn package. Does it have to be enabled during build? Thank you very much in advance!

kerberizer commented on 2016-02-15 22:28 (UTC)

[NOTICE] The D12834 patch is rebased and Clang should build fine now.

kerberizer commented on 2016-02-15 19:16 (UTC)

[NOTICE] There is again a problem with the GCC abi_tag support patch. I'll be looking into it, but I'm rather busy, so unfortunately I cannot promise anything on how long it'll take.

kerberizer commented on 2016-02-03 09:42 (UTC)

[NOTICE] The D12834 patch is rebased and should apply cleanly now.