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

Required by (2179)

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

kerberizer commented on 2017-12-12 19:09 (UTC)

@xDShot, have you followed the procedure, described here: https://github.com/kerberizer/llvm-svn#signature-unknown-trust-error

xDShot commented on 2017-12-12 19:01 (UTC)

error: llvm-svn: signature from "Luchesar V. ILIEV (Arch Linux package signing key) luchesar.iliev@gmail.com" is unknown trust error: failed to update llvm-svn (invalid or corrupted database (PGP signature)) error: database 'llvm-svn' is not valid (invalid or corrupted database (PGP signature))

kerberizer commented on 2017-12-12 15:53 (UTC)

@lahwaacz, apparently that test still needs (7.0 <= CUDA <= 8.0). Have you tried skipping the tests? It could be simply a test that hadn't been properly updated, though I don't have any experience with CUDA, so this is just a shot in the dark.

lahwaacz commented on 2017-12-12 15:22 (UTC)

I need to build clang-svn because clang 5.0 does not support CUDA 9.0. The -svn version seems to work, but there is a test failing with CUDA 9.0:

FAIL: Clang :: Driver/unknown-std.cpp (4403 of 11748)
******************** TEST 'Clang :: Driver/unknown-std.cpp' FAILED ********************
Script:
--
not /home/klinkovsky/build/builddir/llvm-svn/src/build/bin/clang /home/klinkovsky/build/builddir/llvm-svn/src/llvm/tools/clang/test/Driver/unknown-std.cpp -std=foobar -c 2>&1 | /home/klinkovsky/build/builddir/llvm-svn/src/build/bin/FileCheck --match-full-lines /home/klinkovsky/build/builddir/llvm-svn/src/llvm/tools/clang/test/Driver/unknown-std.cpp
not /home/klinkovsky/build/builddir/llvm-svn/src/build/bin/clang -x objective-c++ /home/klinkovsky/build/builddir/llvm-svn/src/llvm/tools/clang/test/Driver/unknown-std.cpp -std=foobar -c 2>&1 | /home/klinkovsky/build/builddir/llvm-svn/src/build/bin/FileCheck --match-full-lines /home/klinkovsky/build/builddir/llvm-svn/src/llvm/tools/clang/test/Driver/unknown-std.cpp
not /home/klinkovsky/build/builddir/llvm-svn/src/build/bin/clang -x cuda -nocudainc -nocudalib /home/klinkovsky/build/builddir/llvm-svn/src/llvm/tools/clang/test/Driver/unknown-std.cpp -std=foobar -c 2>&1 | /home/klinkovsky/build/builddir/llvm-svn/src/build/bin/FileCheck --match-full-lines --check-prefix=CHECK --check-prefix=CUDA /home/klinkovsky/build/builddir/llvm-svn/src/llvm/tools/clang/test/Driver/unknown-std.cpp
--
Exit Code: 1

Command Output (stderr):
--
/home/klinkovsky/build/builddir/llvm-svn/src/llvm/tools/clang/test/Driver/unknown-std.cpp:9:11: error: expected string not found in input
// CHECK: error: invalid value 'foobar' in '-std=foobar'
          ^
<stdin>:1:1: note: scanning from here
clang-6.0: error: GPU arch sm_20 is supported by CUDA versions between 7.0 and 8.0 (inclusive), but installation at /usr/local/cuda is 9.0. Use --cuda-path to specify a different CUDA install, pass a different GPU arch with --cuda-gpu-arch, or pass --no-cuda-version-check.
^
<stdin>:1:10: note: possible intended match here
clang-6.0: error: GPU arch sm_20 is supported by CUDA versions between 7.0 and 8.0 (inclusive), but installation at /usr/local/cuda is 9.0. Use --cuda-path to specify a different CUDA install, pass a different GPU arch with --cuda-gpu-arch, or pass --no-cuda-version-check.
         ^

--

kerberizer commented on 2017-12-12 10:33 (UTC)

@xDShot, indeed, https was not working. Should be fixed now, thanks! Concerning the PGP problem, what exactly is the error message?

xDShot commented on 2017-12-12 04:15 (UTC) (edited on 2017-12-12 04:15 (UTC) by xDShot)

llvm-svn repository is broken. It only works with non-https server, and there's an error in pgp signature.

kerberizer commented on 2017-11-17 16:44 (UTC)

Considering nobody replied, I guess i686 is hardly used. As the official Arch mirrors have already been stripped from the i686 packages, I've disabled the builds for that architecture too. Thus, the binary repo is now x86_64 only. If anyone still needs i686 prebuilt packages, I've saved the last built ones here: http://repos.uni-plovdiv.net/archlinux/llvm-svn-i686/ It's in the standard repo format, so you can use it in pacman.conf, replacing the section '[llvm-svn]' with '[llvm-svn-i686]', but please do note that this repo is _not_ going to be updated. As for the PKGBUILD itself, for the time being I'll be keeping i686 in the arch array and any i686 specific code, if anyone is going to build it themselves on this architecture. NB: The above concerns only the i686 builds. The lib32-{llvm,clang}-svn packages in particular will continue to be automatically built and supported.

kerberizer commented on 2017-11-06 13:07 (UTC) (edited on 2017-11-06 13:12 (UTC) by kerberizer)

[IMPORTANT] This concerns mostly the users of the binary repo, but may still be somewhat relevant to anyone else. As you probably know, i686 is no longer supported in Arch, and by the end of November all i686 packages will be removed from the mirrors. How many of you, if any at all, use the llvm-svn packages on i686? I'd like to get an idea whether it's worth the effort to continue building for i686. Edit: Clarified that the question was specifically about the llvm-svn packages.

msca8h commented on 2017-11-01 05:58 (UTC) (edited on 2017-11-01 06:03 (UTC) by msca8h)

Hi, I built clang-svn with RTTI off and assertions off. About 47 tests failed. I added an issue https://github.com/kerberizer/llvm-svn/issues/19

kerberizer commented on 2017-10-28 15:06 (UTC)

@SolarAquarion, thank you! Committed.

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