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.012336
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 .. 63 64 65 66 67 68 69 70 Next › Last »

WFCody commented on 2011-05-03 15:29 (UTC)

@heftig Another alternative is the self-hosting lll-git package (sorry for blowing my own horn) https://aur.archlinux.org/packages.php?ID=45733 I am currently considering the possibility of including compiler-rt in the build to completely avoid libgcc dependency. Feedback on the package is welcome :)

heftig commented on 2011-04-12 22:55 (UTC)

This is on hiatus for a while until I get it to build again. In the meantime, I recommend clang from [community-testing]: It provides the same patches and isn't broken by gcc 4.6.

jedbrown commented on 2011-02-23 18:55 (UTC)

Please also change the symlink to what is shown below (it is no longer llvm/libLLVMgold.so). # Symlink the gold plugin where clang expects it ln -s "llvm/LLVMgold.so" "$pkgdir/usr/lib/LLVMgold.so"

jedbrown commented on 2011-02-23 18:28 (UTC)

The path "Release/bin/clang" is hard-coded, but you have logic to create a debug build when the strip option is disabled (which puts everything in a different build directory).

<deleted-account> commented on 2011-02-16 15:06 (UTC)

OMG these C++ error messages are so sweet :D

<deleted-account> commented on 2011-02-16 15:00 (UTC)

I installed gcc44 from aur (but bumped it from 4.4.4 to 4.4.5) and made these changes to clang http://pastebin.com/kyVpC7sM Works like a charm, except that I get linker problems when linking to a boost lib that was compiled with gcc-4.5 -____- @big_gie thanks, I added myself to the CC list of this bug. This is certainly a good workaround, but I feel more comfortable to have clang look at the right place to begin with.

big_gie commented on 2011-02-16 13:19 (UTC)

Here are the CFLAGS I need to add when compiling something with clang with gcc 4.5 installed: -I/opt/gcc34/include/c++/3.4.6 -I/opt/gcc34/include/c++/3.4.6/x86_64-unknown-linux-gnu -nostdinc++

big_gie commented on 2011-02-16 12:53 (UTC)

@MaikB: Yes, it's a known issue. See http://llvm.org/bugs/show_bug.cgi?id=7069

<deleted-account> commented on 2011-02-16 11:33 (UTC)

Note: At the moment clang isn't able to handle all bits gcc-4.5s c++ standard library. It uses some c++0x features that clang doesn't support yet, see http://comments.gmane.org/gmane.comp.compilers.clang.devel/10747 . I'm building gcc44 from aur now to see what has to be done to make it work.

« First ‹ Previous 1 .. 63 64 65 66 67 68 69 70 Next › Last »