Please sync with llvm from [extra] and, if possible, add necessarry files required to have lib32-llvm-svn, which are also available in [extra].
Search Criteria
Package Details: llvm-ocaml-git 18.0.0_r484887.953ae94149f0-1
Package Actions
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) |
Dependencies (28)
- llvm-gitAUR
- ocaml
- ocaml-ctypes
- cmake (cmake-gitAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- jsoncpp (jsoncpp-cmake-gitAUR, jsoncpp-cmakeAUR, jsoncpp-gitAUR) (make)
- libedit (make)
- libffi (libffi-gitAUR) (make)
- libxml2 (libxml2-gitAUR, libxml2-2.9AUR) (make)
- lldb (llvm-rocm-gitAUR, llvm-gitAUR) (make)
- lua53 (make)
- ncurses (ncurses-gitAUR) (make)
- ninja (ninja-kitwareAUR, ninja-memAUR, ninja-fuchsia-gitAUR, ninja-gitAUR, ninja-jobserverAUR) (make)
- ocaml (make)
- ocaml-ctypes (make)
- ocaml-findlib (make)
- ocaml-stdlib-shims (make)
- ocl-icd (khronos-ocl-icd-gitAUR, khronos-ocl-icdAUR) (make)
- opencl-headers (opencl-headers-gitAUR) (make)
- python (python37AUR, python311AUR, python310AUR) (make)
- python-myst-parser (python-myst-parser018AUR) (make)
- python-recommonmark (make)
- python-setuptools (make)
- python-six (make)
- python-sphinx (python-sphinx-gitAUR) (make)
- swig (swig-gitAUR) (make)
- z3 (z3-gitAUR) (make)
- python-psutil (check)
Required by (0)
Sources (2)
Latest Comments
« First ‹ Previous 1 .. 54 55 56 57 58 59 60 61 62 63 64 .. 70 Next › Last »
Krejzi commented on 2013-12-08 17:42 (UTC)
justinzane commented on 2013-11-27 06:03 (UTC)
This is the tools/gold/README:
This directory contains a plugin that is designed to work with binutils
gold linker. At present time, this is not the default linker in
binutils, and the default build of gold does not support plugins.
Obtaining binutils:
cvs -z 9 -d :pserver:anoncvs@sourceware.org:/cvs/src login
{enter "anoncvs" as the password}
cvs -z 9 -d :pserver:anoncvs@sourceware.org:/cvs/src co binutils
This will create a src/ directory. Make a build/ directory and from
there configure binutils with "../src/configure --enable-gold --enable-plugins".
Then build binutils with "make all-gold".
To build the LLVMgold plugin, configure LLVM with the option
--with-binutils-include=/path/to/binutils/src/include/ --enable-pic. To use the
plugin, run "ld-new --plugin /path/to/LLVMgold.so".
Without PIC libLTO and LLVMgold are not being built (because they would fail
link on x86-64 with a relocation error: PIC and non-PIC can't be combined).
As an alternative to passing --enable-pic, you can use 'make ENABLE_PIC=1' in
your entire LLVM build.
How on earth to I edit the PKGBUILD for this?
justinzane commented on 2013-11-27 06:00 (UTC)
LLVMgold.so, the linker plugin seems to have disappeared after replacing the repo clang with this; which breaks a number of my builds. How to recover it?
xdegaye commented on 2013-11-12 17:00 (UTC)
@ aksr
lldb also crashes on my VmWare VM, see
http://llvm.org/bugs/show_bug.cgi?id=17802
You could check if you have the same backtrace of the crash, either running lldb
from gdb or examining the core file with gdb.
To disable the handling of core dumps by systemd-coredumpctl(1), see
https://wiki.archlinux.org/index.php/Systemd#Disabling_application_crash_dumps_journaling
aksr commented on 2013-11-12 09:14 (UTC)
No, something else is missing. I reinstalled everything, still, the same problem persists.
mtahmed commented on 2013-11-12 04:27 (UTC)
You could have corrupt llvm libraries.
Could you first re-install llvm-libs and then try re-compiling and re-installing this AUR package and let me know?
schulmar commented on 2013-11-11 16:41 (UTC)
It seems this version is too old. You could try to build with gcc instead of clang. The new package version does not depend on clang to build lldb anymore. It takes a bit longer but should be possible (I tried it with the repository version yesterday). Another thing you could try would be to remove the lldb part from the PKGBUILD, build and install LLVM+clang and then try the full install which should then benefit from the newly installed clang version.
aksr commented on 2013-11-11 16:22 (UTC)
Version from the official repo: clang version 3.3 (tags/RELEASE_33/final)
aksr commented on 2013-11-11 16:10 (UTC)
Still, it doesn't work. It segfaults if I try to *run* program within it. I'm not sure what could be the problem, since I use compilers (gcc, clang) from the official repositories. I tried to compile other package (which contains lldb), but with no success: https://privatepaste.com/2955f51a7c .
schulmar commented on 2013-11-11 16:07 (UTC)
Which version of clang are you using for compilation?
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
This package
llvm-minimal-git
packages created & maintained by Lordheavy, an arch developer
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.
llvm-git
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.
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.