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

Required by (2198)

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 .. 25 26 27 28 29 30 31 32 33 34 35 .. 70 Next › Last »

kerberizer commented on 2018-07-12 09:46 (UTC)

@Lone_Wolf, thank you very much!

Lone_Wolf commented on 2018-07-12 09:38 (UTC)

Solved in meson 0.47.1 .

lahwaacz commented on 2018-07-05 13:46 (UTC) (edited on 2018-07-05 13:47 (UTC) by lahwaacz)

I was trying to rebuild mesa with llvm-svn but got this error:

src/gallium/targets/opencl/meson.build:36:0: ERROR:  C++ library 'clangCodeGen' not found

It seems that the clang package provides /usr/lib/libclangCodeGen.so, but clang-svn provides /usr/lib/libclangCodeGen.a which seems not to be enough...

kerberizer commented on 2018-06-02 22:10 (UTC)

The "pkgver in depends is not allowed to be empty" error should be fixed now.

kerberizer commented on 2018-05-31 22:56 (UTC)

@Lone_Wolf, thanks! Indeed, without OCaml installed, this would leave ${_ocamlver} empty, and apparently now makepkg checks this and complains. I think we can change _ocamlver() to something like this...

{ pacman -Q ocaml 2>/dev/null || echo 'ocaml 0.0.0-0' ;} \
    | awk '{ print $2 }' | cut -d - -f 1 | cut -d . -f 1,2,3

I'll leave it for tomorrow though as it's getting rather late here.

Lone_Wolf commented on 2018-05-31 20:12 (UTC) 

$ makepkg -Crs
error: package 'ocaml' was not found
==> ERROR: pkgver in depends is not allowed to be empty.
$

Everything worked a week ago, i think it may be related to the upgrade to pacman 5.1 .

The only reference i could find of ocaml without suffix is in package_llvm-ocaml-svn() .

package_llvm-ocaml-svn() {
    pkgdesc='OCaml bindings for LLVM'
    depends=(
        "llvm-svn=${pkgver}-${pkgrel}"
        "ocaml=$(_ocamlver)"
        'ocaml-ctypes'
    )

Replacing ""ocaml=$(_ocamlver)" with 'ocaml' made the build go through.

levisraju commented on 2018-05-24 04:27 (UTC)

In the PKGBUILD, comment out the lines within the funtion check() for a successful build.

kerberizer commented on 2018-05-21 10:47 (UTC)

@yans, I have no idea, sorry. As a temporary solution, you can just comment out the tests in the PKGBUILD or use the --nocheck option of makepkg. In general, it's good to have these things reported upstream, but I usually assume they must be aware already, as they are likely running their own automated build systems.

Speaking of which, if somebody feels they could provide more active maintenance to these packages, please step forward. The reality is that I'm not using them any more and my job is putting more pressure on me, hence why in the last year or so I've restricted myself to only fixing complete breakages or trivial problems and, of course, maintaining the binary repo. I can continue doing that, but not much more, I'm afraid, at least for the foreseeable future.

yans commented on 2018-05-20 22:05 (UTC) (edited on 2018-05-20 22:05 (UTC) by yans)

Failing Tests (2):

LLVM :: tools/gold/X86/comdat.ll

LLVM :: tools/gold/X86/visibility.ll

Why? https://hastebin.com/ahidopuqos.md

Lone_Wolf commented on 2018-05-05 12:13 (UTC) (edited on 2018-05-05 15:06 (UTC) by Lone_Wolf)

no problems at all except some tests failing (--nocheck solves that).

Ignore what i earlier said about symlinks problems, it was user error.

« First ‹ Previous 1 .. 25 26 27 28 29 30 31 32 33 34 35 .. 70 Next › Last »