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.008894
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 .. 28 29 30 31 32 33 34 35 36 37 38 .. 70 Next › Last »

SolarAquarion commented on 2017-10-27 18:58 (UTC)

@kerberizer add this export LDFLAGS="$LDFLAGS -pthread -lpthread -lm"

kerberizer commented on 2017-10-26 19:07 (UTC)

@Griever thanks! Let's see if they fix it fast (usually I don't pay much attention to these problems, as they're more or less inevitable on the master/trunk branches and get caught by any CI system the project is using, so after a few days at most they get fixed upstream).

Griever commented on 2017-10-26 18:24 (UTC)

Here's the upstream bug report about the lldb pthread issue: https://bugs.llvm.org/show_bug.cgi?id=35053 It lists what commit broke it and a potential fix.

kerberizer commented on 2017-10-26 17:56 (UTC)

I am aware of the problem (this is the reason why the binary repo has also not been updated recently). Apparently, it's a linking problem, so it isn't a matter of missing dependencies. Rather, it may be a problem of incorrect parameters passed to the linker, like e.g. in this (unrelated) case: https://github.com/openssl/openssl/issues/3884 Unfortunately, right now I don't have time to properly dissect it further. If someone comes up with a solution, please do post it here or on GitHub.

blauerhunger commented on 2017-10-26 17:38 (UTC)

I'm having the same problem as SolarAquarion in a clean chroot (building with extra-x86_64-build). Are there some makedeps missing?

SolarAquarion commented on 2017-10-26 11:00 (UTC)

[ 93%] Linking CXX executable ../../../../bin/lldb-svn ../../../../lib/liblldbUtility.a(Log.cpp.o): In function `lldb_private::Log::Initialize()': Log.cpp:(.text._ZN12lldb_private3Log10InitializeEv+0x11): undefined reference to `pthread_atfork' collect2: error: ld returned 1 exit status make[2]: *** [tools/lldb/tools/lldb-server/CMakeFiles/lldb-server.dir/build.make:342: bin/lldb-server] Error 1 make[1]: *** [CMakeFiles/Makefile2:82665: tools/lldb/tools/lldb-server/CMakeFiles/lldb-server.dir/all] Error

pr0dukter commented on 2017-10-18 23:28 (UTC)

Lone wolf: yes and i cant build mesa-git with gcc or clang gcc error is llvm/invocation.cpp:109:52: required from here ./util/adaptor.hpp:56:10: warning: mangled name for ‘clover::detail::iterator_adaptor<F, Is>::iterator_adaptor(F, std::tuple<_Elements ...>&&) [with F = std::_Mem_fn<const char* (std::__cxx11::basic_string<char>::*)() const noexcept>; Is = {__gnu_cxx::__normal_iterator<const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >*, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >}]’ will change in C++17 because the exception specification is part of a function type [-Wnoexcept-type] iterator_adaptor(F f, std::tuple<Is...> &&its) : clang error is similar something about std::clover going back to 5.0 for now i suppose, if none of this is helpful and is just spamming the useful comments feel free to delete

Lone_Wolf commented on 2017-10-17 13:38 (UTC) (edited on 2017-10-17 13:39 (UTC) by Lone_Wolf)

You did make sure that the mesa/mesa-git you were running was build against the same llvm/lvvm-svn version you had installed at that time ? That sounds confusing, trying to rephrase : when you had llvm 5 installed, was the installed mesa build against that version ? When llvm-svn was installed, was installed mesa built against the same version ?

pr0dukter commented on 2017-10-17 04:55 (UTC)

theres something different between llvm-5.0.0 and llvm-svn here that stops amdgpu from loading dri3 and/or dri2 glamor and/or glx resulting in no rotation for any display have tried with various 4.12 - 4.13 kernels drm-nexts thru 4.15 and all xorg-server- dev/gits and required xf86-video's and git counterparts (with and without correct proofread, previously working xorg.conf's when necessary

kerberizer commented on 2017-09-29 12:00 (UTC) (edited on 2017-09-29 12:01 (UTC) by kerberizer)

RE missing editline/readline.h errors: Indeed, “[a]s a general rule, everything within a split packages depends array should be in the global makedepends array (...)”[1], so libedit is now an explicit makedepend. This should fix the missing header issue. @pr0dukter, the recommended and only supported build method is thru a clean chroot. You can find some instructions on GitHub (see the pinned comment). There's also a binary repo if you're fine with using precompiled binaries. Edit: fixed small typo. --- 1. https://bbs.archlinux.org/viewtopic.php?pid=591614#p591614

« First ‹ Previous 1 .. 28 29 30 31 32 33 34 35 36 37 38 .. 70 Next › Last »