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.005348
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 .. 11 12 13 14 15 16 17 18 19 20 21 .. 70 Next › Last »

gardotd426 commented on 2020-03-06 15:17 (UTC)

@nstgc Actually I just tried it with removing python-yaml first and it still failed with two tests: 


Failing Tests (2):
    LLVM :: tools/gold/X86/thinlto_weak_library.ll
    LLVM :: tools/gold/X86/v1.16/wrap-2.ll

nstgc commented on 2020-03-06 14:16 (UTC)

@gardotd426 This is just my two cents as a two bit user, but I don't see why it's worth taking chances when you can easily run pacman -Rdd python-yaml and then reinstall it after compiling is down. You could even make it a one liner:

sudo pacman -Rdd python-yaml && makepkg -sir && sudo pacman -S --noconfirm python-yaml

Assuming you didn't delete the package archive, that shouldn't take long.

gardotd426 commented on 2020-03-06 14:08 (UTC) (edited on 2020-03-06 15:14 (UTC) by gardotd426)

So does python-yaml need to be removed before this will properly work, or is it enough to just use --nocheck?

nstgc commented on 2020-03-05 14:54 (UTC)

@Lone_Wolf Thanks for that! python-yaml is required by lutris, but I can uninstall that long enough to build this. And I will take your advise and build llvm-minimum-git instead. It has this same issue by the way.

Lone_Wolf commented on 2020-03-05 14:39 (UTC)

I've confirmed the test failure occurs only with python-yaml present and reported the bug.

https://bugs.llvm.org/show_bug.cgi?id=45119

Lone_Wolf commented on 2020-03-05 00:53 (UTC)

Yup, those are the log files I needed.

File "/home/nstgc5/Installers/llvm-git.aur/src/llvm-project/llvm/tools/opt-viewer/opt-viewer.py", line 200, in render_entry
    escaped_name = cgi.escape(r.DemangledFunctionName)
AttributeError: module 'cgi' has no attribute 'escape'

cgi.escape was removed in python 3.8, so the error itself is correct. Not sure why llvm tools want to use deprecated functionality.

The log also mentions you have python module yaml , and yaml is not present in my build environment .

  • llvm git/svn versions are tricky to build
  • When problems occur, I verify they're not due to my build machine by building in a clean chroot. check https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_clean_chroot
  • mesa-git supports all videocards supported by stock mesa, no need to wait.
  • Incase you only need llvm trunk for mesa-git, llvm-minimal-git is probably a better choice.

nstgc commented on 2020-03-04 16:09 (UTC)

@Lone_Worlf These are the logs I think you are looking for:
https://gist.github.com/nstgc/34b6824016e861a0e310656793a7828c
https://gist.github.com/nstgc/ea881f98eeec5c4cc8db704f5bb1f218

nstgc commented on 2020-03-04 14:49 (UTC) (edited on 2020-03-04 14:50 (UTC) by nstgc)

@Lone_Wolf A question (sorry). I was reading through the stickies for llvm-minimal-git and it mentioned errors for non-amdgpu (and to ignore them). I'm building llvm (and mesa) ahead of installing a new video. Should I wait until I have the AMD card in my computer before compiling this stuff? I've never compiled drivers or kernels before so I'm not really sure of best practices.

nstgc commented on 2020-03-04 14:18 (UTC)

@Lone_Wolf This is embarrassing, but I've never really gone to this extent to get something in the AUR installed so I don't know what you mean by "log files". Reading through man makepkg I'm guessing you mean for me to use the -L switch like, LOGDEST=$PWD/logs makepkg -sirL? This?

Lone_Wolf commented on 2020-03-04 13:59 (UTC) (edited on 2020-03-04 13:59 (UTC) by Lone_Wolf)

lldb tests re-enabled.

While looking at lldb cmakelists.txt for options to solve the test failure, I noticed an option to use system-provided python-six . Using that option allowed to remove a workaround from the package_llvm-git() function.

nstgc : post log files of the build somewhere. I'll run a clean chroot build to verify dependencies.

« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 .. 70 Next › Last »