A note on LLDB.
The official llvm set of packages includes lldb, and several days ago I actually tried adding it here -- not realizing that there is already an independent lldb-svn package here on AUR. I've contacted its maintainers and asked them if they would agree merging their package into llvm-svn, as I think this would allow for much greater consistency and even ease of support. I haven't yet received a reply, but I guess they are most likely very busy.
In short, guys, I'd be happy to hear if you want to see LLDB here.
And for those who build the packages yourself and want LLDB, you can use the GitHub repo. There's a branch enh/lldb-svn, which is rebased to master regularly.
https://github.com/kerberizer/llvm-svn/tree/enh/lldb-svn
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.005925 |
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 (opencl-icd-loaderAUR, khronos-ocl-icd-loaderAUR, khronos-ocl-icd-gitAUR) (make)
- opencl-headers (opencl-headers-gitAUR) (make)
- python (python37AUR, python311AUR, python310AUR) (make)
- python-myst-parser (python-myst-parser018AUR) (make)
- python-recommonmarkAUR (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 (2230)
- 0ad-data-git (requires llvm) (make)
- 0ad-git (requires llvm) (make)
- 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-git (requires llvm) (make)
- aero2solver (requires clang) (make)
- aewm++ (requires clang) (make)
- air-git (requires clang) (make)
- aircrack-ng-clang-git (requires clang) (make)
- alvr (requires clang) (make)
- alvr-git (requires clang) (make)
- alvr-nvidia (requires clang) (make)
- ambuild-git (requires clang)
- amdapp-sdk (requires llvm)
- Show 2210 more...
Sources (2)
Latest Comments
« First ‹ Previous 1 .. 44 45 46 47 48 49 50 51 52 53 54 .. 70 Next › Last »
kerberizer commented on 2015-09-06 19:06 (UTC)
kerberizer commented on 2015-09-06 18:48 (UTC)
@yurikoles, not sure that I understand your request. Could you please elaborate a bit more?
yurikoles commented on 2015-09-06 15:55 (UTC)
Please extract "trunk" to variable "branch". It may be for example "branches/release_37" or "tags/RELEASE_370/final". I have tested all 3 values.
kerberizer commented on 2015-09-06 11:16 (UTC)
[HEADS UP] Rebuild required
I've committed the change that should fix the shared library breakage. This might require some action on your side, namely:
* If you build the packages yourself and have last rebuilt them more recently than 08:30 AM UTC yesterday, Sept 5th, please do rebuild them again now.
* If you use the binary repo and have last updated your packages from the repo more recently than 09:00 AM UTC yesterday, Sept 5th, please wait until about 11:45 AM UTC today, Sept 6th (half an hour from now; the new packages are still being built), and update again.
As usual, please let me know if you find any problems, and especially if they are of the "undefined reference" type when linking to libLLVM, please report them here: https://github.com/kerberizer/llvm-svn/issues/2
kerberizer commented on 2015-09-06 09:48 (UTC)
For those curious enough, this is the commit that breaks our build, due to the changes to tools/llvm-shlib/CMakeLists.txt, which we parse in order to determine which components we want exported from the shared lib (and which, in turn, we make because of the bug in exporting the necessary symbols on Linux).
https://github.com/llvm-mirror/llvm/commit/f5148ebe0ac2e89cf991b7d6e01778bbb8d55034
I'm testing at the moment a changed PKGBUILD that should hopefully produce a working shared lib again. Sorry for any inconvenience.
kerberizer commented on 2015-09-06 09:25 (UTC)
[WARNING] The shared library seems broken at the moment, with many symbols not being exported. I'm looking into this.
kerberizer commented on 2015-09-03 14:53 (UTC)
[NOTICE] Possible instability ahead
Guys, please take note that in the next days I'll be working on a probably major rework of the PKGBUILD. The reason is that the critical bug with LLVM not exporting the expected symbols has (likely) been fixed upstream at last. This means that the bunch of "awk-ward" dirty tricks currently in the PKGBUILD is probably not needed any more, but I'll have to test this thoroughly. I'll try to make sure that the PKGBUILD stays stable, but just be warned in advance. I'll also post the usual "heads up" once any such changes get committed here.
References:
* https://github.com/kerberizer/llvm-svn/issues/2
* https://llvm.org/bugs/show_bug.cgi?id=24157
* https://github.com/llvm-mirror/llvm/commit/10add60748226d67d3a1e4d1a8175f798a053708
kerberizer commented on 2015-09-02 21:47 (UTC)
@Eriner, not sure if that could've been the case here, but sometimes various transient build errors happen just because that's the master branch, with all development constantly going on, and, though rarely, commits do happen to break things, even that badly. They are also usually fixed very quickly, so just waiting an hour or so and building again from fresh source code is all that is needed.
Eriner commented on 2015-09-02 20:15 (UTC)
Ah, after completely removing the svn repo and rebuilding it seems to have fixed itself. So if anyone gets the same error as below, remove your llvm-svn folder, git pull, rebuild.
Eriner commented on 2015-09-02 20:08 (UTC)
Anyone getting errors like this? https://gist.github.com/Eriner/30274ab4da191d06724c
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.