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.010051
First Submitted: 2018-12-05 13:56 (UTC)
Last Updated: 2024-04-17 08:17 (UTC)

Required by (127)

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 .. 21 22 23 24 25 26 27 28 29 30 31 .. 70 Next › Last »

zor1984qq commented on 2019-03-18 11:07 (UTC)

[ 18%] Linking CXX static library ../../libLLVMDebugInfoPDB.a [ 18%] Built target LLVMDebugInfoPDB make: *** [Makefile:152: all] Ошибка 2 ==> ОШИБКА: Произошел сбой в build(). Прерывание... 2019-03-18 13:59:12,373 - wrappers - makepkg - ERROR - makepkg query ['makepkg', '-cf', '--noconfirm'] failed in directory /home/sergey/.cache/aurman/llvm-git

BillFleming commented on 2019-03-07 11:03 (UTC)

Please add python-recommonmark to dependencies.

kerberizer commented on 2019-02-18 23:19 (UTC)

Just to let you know, guys, that I'm slowly making some progress. It's not a tremendous amount of work actually, but unfortunately I rarely have the necessary time to focus on it and I also want to make sure it will work reasonably well. I really appreciate your patience and understanding. I guess that in the meantime those who build the packages on their own already use some workarounds, and for those who wait for the binary repos, I really hope that in the next few days I'll be ready (but, please, take this with a grain of salt too).

sleepprogger commented on 2019-02-02 18:58 (UTC)

@PedroHLC:

It looks like some files moved. This is prob not the correct way to go but changing that line to

mv -f "${srcdir}"/build/lib/{BugpointPasses,LLVMgold,LLVMHello}.so "${srcdir}/"

and adding a rm -f "${pkgdir}"/usr/lib/LLVMgold.so

to prevent LLVMgold.so to be in both llvm-libs and llvm solved the problem for me. `

kerberizer commented on 2019-02-01 16:47 (UTC)

@clap22, I'm very sorry for not paying enough attention to these packages and the repo lately. I've been through some major changes in my day job that really consumed all my time. But I'm not abandoning the packages. As always, some help or even a new maintainer with more free time (and perhaps more expertise) will be welcome, but I'll continue doing whatever I can to keep them and the repo alive and current.

Anyhow, I started working on switching the packages to Ninja, which is what, apparently, nowadays most LLVM devs use. There are some problems that I need to deal with though—I don't think they are serious, but can't tell yet how much time I'll need (FWIW, llvm in extra has been using Ninja fine for some time).

Something else that I'm considering—and which we've discussed with @Lone_Wolf some time ago—is splitting clang into its own package (or pkgbase). I'm mentioning this because it might turn out to be best done together with the Ninja switch. If it can wait, though, I won't bother with it for now.

Finally, some of you are perhaps aware that LLVM is in the process of transition from Subversion to Git for its source code. Once it gets finalized we'll need to switch to Git, and the obvious question is what's going to happen to the package names: keep them (it really doesn't matter what VCS is used in the package), or rename/move to -git names. I'll probably ask in aur-general@ what's considered best practice in such cases, but if somebody here already knows, please do comment.

clap22 commented on 2019-02-01 02:58 (UTC)

I miss your binaries, are you abandoning them?

kerberizer commented on 2019-01-31 09:54 (UTC)

@PedroHLC, it is broken, indeed. I'll see to have it fixed. Thank you!

PedroHLC commented on 2019-01-30 15:56 (UTC) (edited on 2019-01-30 15:57 (UTC) by PedroHLC)

On line:

mv -f "${pkgdir}"/usr/lib/{BugpointPasses,LLVMgold,LLVMHello}.so "${srcdir}/"

These files are not being generated for me:

-- Installing: /home/main-builder/pkgwork/pkg/llvm-svn/usr/lib/cmake/llvm/./CheckAtomic.cmake
mv: cannot stat '/home/main-builder/pkgwork/pkg/llvm-svn/usr/lib/BugpointPasses.so': No such file or directory
mv: cannot stat '/home/main-builder/pkgwork/pkg/llvm-svn/usr/lib/LLVMHello.so': No such file or directory
==> ERROR: A failure occurred in package_llvm-svn().

Haxk20 commented on 2019-01-25 11:20 (UTC)

There are multiple issues with packaging. make check-clang make check-polly And also it says that those are not valid make commands. Please update the PKGBUILD to fix issues with LLVM9.

« First ‹ Previous 1 .. 21 22 23 24 25 26 27 28 29 30 31 .. 70 Next › Last »