Package Details: llvm-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: LLVM development version. includes clang and many other tools
Upstream URL: https://llvm.org/
Keywords: clang git lld lldb llvm polly
Licenses: custom:Apache 2.0 with LLVM Exception
Conflicts: clang, compiler-rt, lld, lldb, llvm, polly
Provides: aur-llvm-git, clang, clang-git, compiler-rt, compiler-rt-git, lld, lld-git, lldb, lldb-git, llvm, polly, polly-git
Submitter: yurikoles
Maintainer: rjahanbakhshi
Last Packager: rjahanbakhshi
Votes: 118
Popularity: 0.010693
First Submitted: 2018-12-05 13:56 (UTC)
Last Updated: 2024-04-17 08:17 (UTC)

Required by (2205)

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

kerberizer commented on 2016-02-03 08:54 (UTC)

[NOTICE] There is again a problem with the GCC abi_tag support patch. I'll be looking into it.

kerberizer commented on 2016-01-30 01:01 (UTC)

[NOTICE] pkgver() is fixed and should again produce the correct version.

kerberizer commented on 2016-01-29 23:51 (UTC)

[NOTICE] There is a problem with pkgver() because of the final retirement of the autotools build and files. While we have been using Cmake in our PKGBUILD for a long time already, pkgver() still relies on the now non-existent autotools files. I'm working on a fix that should be ready really soon.

kerberizer commented on 2016-01-20 11:22 (UTC)

The package is updated: the new patch should now apply cleanly; the Clang segfault does seem fixed too. The binary repo will be updated shortly as well.

kerberizer commented on 2016-01-20 09:57 (UTC)

@mnovick1988, thanks for pointing that out. Speaking of this, there's been a newer patch on http://reviews.llvm.org/D12834 for a few days now, which I've been planning to push here, but just couldn't find the time for it. It still needed a couple of updates to apply cleanly to latest code, and as soon as I'm finished testing it, I'll update the package. Perhaps more importantly, according to @foutrelis (who maintains the official LLVM/Clang Arch packages), this new version of the patch solves the segmentation faults with Clang in some specific cases, which were mentioned several comments below.

EndlessEden commented on 2016-01-20 03:04 (UTC)

patches are failing

kerberizer commented on 2016-01-14 10:34 (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, * you use `{lib32-,}llvm-svn` from AUR, * you have upgraded the `{lib32-,}llvm-svn` packages during the last ~24 hours, whether by compiling yourself or from the `llvm-svn` binary repo, then please note that you MUST recompile the Mesa packages (or possibly upgrade again from the `mesa-git` binary repo you use). The reason is the recent branching of LLVM/Clang 3.8 and bumping the development version to 3.9, which also affects the shared library version. If Mesa is not recompiled, with the new {lib32-,}llvm-svn packages you'll face errors of the type: gbm: Last dlopen error: libLLVM-3.8svn.so: cannot open shared object file: No such file or directory (EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/swrast_dri.so failed (libLLVM-3.8svn.so: cannot open shared object file: No such file or directory) Please note that for 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.

kerberizer commented on 2016-01-14 03:41 (UTC)

[NOTICE] Future release 3.8 has been branched a few hours ago, so welcome to LLVM/Clang 3.9! ;)

kerberizer commented on 2015-12-20 02:07 (UTC)

@zanny, I've just compiled successfully a debug version on my local machine. Is there anything else that you change in the PKGBUILD besides switching CMAKE_BUILD_TYPE from Release to Debug? Also, I noticed the last night that the build would fail several times in a row, most likely due to some problematic commit (it went away before I found time to investigate), so could your problem be just an unfortunate coincidence?

« First ‹ Previous 1 .. 40 41 42 43 44 45 46 47 48 49 50 .. 70 Next › Last »