Package Details: llvm-ocaml-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: OCaml bindings for LLVM
Upstream URL: https://llvm.org/
Keywords: clang git lld lldb llvm polly
Licenses: custom:Apache 2.0 with LLVM Exception
Conflicts: llvm-ocaml
Provides: llvm-ocaml
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)

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 .. 37 38 39 40 41 42 43 44 45 46 47 .. 70 Next › Last »

Lone_Wolf commented on 2016-05-28 13:56 (UTC)

llvm-svn 3.9.0svn_r271112-1 builds fine here. The log shows you were building with yaourt, does the build fail for you when you build with makekpkg ?

gentoofu commented on 2016-05-28 05:24 (UTC)

Am I the only one who's getting this error? http://pastebin.com/PSKbGhd5

kerberizer commented on 2016-05-23 15:14 (UTC)

[NOTICE] The D18035 patch has been updated to the latest revision and the regression tests pass successfully again.

kerberizer commented on 2016-05-21 19:38 (UTC) (edited on 2016-05-21 19:39 (UTC) by kerberizer)

@rectangleboy, thank you for the report. It's a bit confusing that I've been seeing different errors these days: yours is yet another one. Right now, however, the clean code passes all tests without problems, and only with D18035 applied is one test still failing. I haven't had the time to follow the recent commits in detail, so I can only guess that perhaps some of those commits might have caused the regression tests to fail, and eventually got fixed -- but unsurprisingly, the patch didn't get the appropriate fix (since it hasn't yet been committed itself). Long story short, I've informed the patch author about the problem and am looking forward to his reply: http://reviews.llvm.org/D18035

rectangleboy commented on 2016-05-21 07:59 (UTC)

Can confirm. Regression test is killing this build for me. Hopefully this image helps: http://i.imgur.com/NIptD4L.png

kerberizer commented on 2016-05-18 23:18 (UTC)

[NOTICE] Apparently, one of the Clang regression tests has been failing for the last about 24 hours. I'll take a look tomorrow if it isn't connected to the D18035 patch.

kerberizer commented on 2016-05-11 20:53 (UTC)

@wolf, I'm afraid it's not quite possible to use llvm-svn with Mesa from the official Arch package when using the AMD open source drivers. I don't recommend using symlinks either, because the LLVM shared library changes a lot (you'll likely get undefined symbol errors, but that's probably the lesser evil). The only proper solution is building an up-to-date Mesa, preferably from the mesa-git package here in AUR. Or using a prebuilt one from the repos that @lordheavy and I think @Lone_Wolf maintain.

wolf commented on 2016-05-11 19:41 (UTC) (edited on 2016-05-11 19:57 (UTC) by wolf)

This package breaks opengl on my ATI GPU system. The dri looks for libllvm-3.7.so or something. Didn't try if symlink is enough to get it work, will do.

kerberizer commented on 2016-05-09 20:28 (UTC)

[NOTICE] Two small changes, the second of which is still worth paying attention to: * The D18035 patch has been updated to the latest revision: http://reviews.llvm.org/D18035 * The post-build regression tests for LLVM and Clang have been enabled. This may cause the builds to fail sometimes unexpectedly, but there's usually a good reason for that and you'll likely not want to use such builds anyway.

kerberizer commented on 2016-04-20 20:23 (UTC)

@wolf, it's a split package. The same PKGBUILD is used to build all the seven packages listed in the section "Packages" when you look at the package base... https://aur.archlinux.org/pkgbase/llvm-svn/ More information on how the split packages work is available from the Arch wiki... https://wiki.archlinux.org/index.php/PKGBUILD

« First ‹ Previous 1 .. 37 38 39 40 41 42 43 44 45 46 47 .. 70 Next › Last »