At the time of writing, this is the only usable lldb for Arch, due to https://bugs.archlinux.org/task/49974
Search Criteria
Package Details: llvm-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: | 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) |
Dependencies (28)
- llvm-libs-gitAUR
- perl (perl-gitAUR)
- 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)
- python (python37AUR, python311AUR, python310AUR) (optional) – for scripts
Required by (2179)
- aax-bruteforce (requires clang) (make)
- across (requires clang) (make)
- actionfps-client (requires clang) (make)
- actionfps-common (requires clang) (make)
- actionfps-server (requires clang) (make)
- activate-linux (requires clang) (make)
- activate-linux-wayland-git (requires clang) (make)
- adaptivecpp (requires llvm) (make)
- adaptivecpp-common-git (requires clang) (make)
- adaptivecpp-common-git (requires llvm) (make)
- adaptivecpp-cpu-git (requires clang) (make)
- adaptivecpp-cpu-git (requires llvm) (make)
- adaptivecpp-git (requires llvm) (make)
- adaptivecpp-opencl-git (requires clang) (make)
- adaptivecpp-opencl-git (requires llvm) (make)
- adaptivecpp-rocm-git (requires clang) (make)
- adaptivecpp-rocm-git (requires llvm) (make)
- adscript (requires clang) (make)
- adscript (requires llvm)
- aero2solver (requires clang) (make)
- Show 2159 more...
Sources (2)
Latest Comments
« First ‹ Previous 1 .. 33 34 35 36 37 38 39 40 41 42 43 .. 70 Next › Last »
cdkitching commented on 2016-10-17 02:57 (UTC)
kerberizer commented on 2016-10-06 14:20 (UTC)
[HEADS UP] AMD open source driver users: Upgrade of llvm-libs-svn may corrupt your screen
I'm not sure if this is a genuine issue or some random problem with my specific GPU, but with the last upgrade I've just made, the screen turned into complete mess the moment the LLVM shared lib (I suppose) was upgraded. One could actually see the windows been switched and menus opened, but extremely distorted. It was also a relatively soft issue: logout and login back into Gnome fixed it.
Again, this might not relate to you, but be warned: I suggest upgrading either from the console, or at least without anything else open, so that you can reload the GUI or restart the system without much risk to lose data.
kerberizer commented on 2016-10-06 14:11 (UTC)
[NOTICE] The problem with libLTO being present in both 'llvm-libs-svn' and 'llvm-svn' has been fixed. This pertains as well to lib32-llvm-svn.
kerberizer commented on 2016-10-06 08:09 (UTC)
@yousry, thanks for you comment. Let me see if I got you right: if you build Clang with this PKGBUILD, it segfaults on compiling your game, but if you build it on your own, Clangs compiles your game without problems, right?
I'm afraid I can't spot any differences in how you checkout LLVM et al. compared to the PKGBUILD, except for the obvious lack of libc++ in the latter (it also uses svn export, but this shouldn't matter).
Could you possibly share the full CMake command that you use and what make commands you run afterwards as well, please? Might be more convenient if you file a bug here...
https://github.com/kerberizer/llvm-svn/issues
I've already opened an issue myself for the libc++ inclusion. This is a good idea, and I'll see what I can do.
https://github.com/kerberizer/llvm-svn/issues/6
yousry commented on 2016-10-06 06:55 (UTC)
I'm currently trying to create a package for my game: https://github.com/yousry/COOL-The-Game. Clang is hereby a necessary part of the toolchain. Unfortunately a build with this version of clang results in a segfault.
I identified several differences to my build process. I use the following package structure: https://gist.github.com/yousry/fc513f6feb0a586f788747a0a7225f28
I use CMAKE (without Ocaml) with ffi and rt enabled.
Please also consider the inclusion of libc++. This could become useful for system independent builds (For example to support BSDs).
kerberizer commented on 2016-10-05 21:11 (UTC)
[NOTICE] There might be currently some problem with the package, where on installation it gives errors like "/usr/lib/libLTO.so.40 exists in both 'llvm-libs-svn' and 'llvm-svn'". I'll look into this tomorrow.
farseerfc commented on 2016-09-29 03:30 (UTC)
@kerberizer thanks for fixing this
kerberizer commented on 2016-09-28 23:12 (UTC)
[NOTICE] The bug with the OCaml documentation path has been fixed. Thanks again to @farseerfc for reporting this.
If you install the llvm-ocaml-svn package, please have in mind that the HTML documentation now resides in a different place:
old: /usr/share/doc/ocaml/html/
new: /usr/share/doc/llvm/ocaml-html/
On an unrelated note, if anyone is building these packages on i686 (32-bit), I've disabled the LLVM regression tests on that architecture, as they seem to fail often and I'm not quite sure if even upstream cares that much about fixing them. The packages still build fine, and if you'd like so, you may enable the tests by editing the PKGBUILD. Again, this applies only to i686 (32-bit). For x86_64 (64-bit), which I suppose most and likely all of you use, there is no change. Also, this doesn't affect the lib32 compat packages at all.
kerberizer commented on 2016-09-28 18:05 (UTC)
@farseerfc, there's indeed a problem. Guess something changed upstream; I'll see to get it fixed. Thanks for reporting it!
farseerfc commented on 2016-09-28 17:57 (UTC)
build with an error in these 2 days:
mv: cannot stat '/build/llvm-svn/pkg/llvm-svn/usr/share/doc/ocaml': No such file or directory
==> ERROR: A failure occurred in package_llvm-svn().
Aborting...
==> ERROR: Build failed, check /var/lib/archbuild/extra-x86_64/farseerfc/build
How can I fix this problem?
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.