| Git Clone URL: | https://aur.archlinux.org/llvm-git.git (read-only, click to copy) |
|---|---|
| Package Base: | llvm-git |
| Description: | runtime libraries for llvm-git |
| Upstream URL: | https://llvm.org/ |
| Keywords: | clang git lld lldb llvm polly |
| Licenses: | custom:Apache 2.0 with LLVM Exception |
| Conflicts: | llvm-libs |
| Provides: | aur-llvm-libs-git, llvm-libs |
| Submitter: | yurikoles |
| Maintainer: | rjahanbakhshi |
| Last Packager: | rjahanbakhshi |
| Votes: | 118 |
| Popularity: | 0.010693 |
| First Submitted: | 2018-12-05 13:56 (UTC) |
| Last Updated: | 2024-04-17 08:17 (UTC) |
Sinistar, did you also add a hard dependency on that version as a runtime dependency for llvm-git ?
If not, then you have no guarantee the ocaml version at runtime will be the same as the one the package is build against.
I guess the clean way to do this would be to go back to the method used in llvm-svn (and extra/llvm ) and split off the ocaml support into a package_llvm-ocaml-git() function that gets a hard dependency on the specific ocaml version it's build against.
I use this in my PKGBUILD for ocaml version.
_ocaml_ver() {
{ pacman -Q ocaml 2>/dev/null || pacman -Sp --print-format '%n %v' ocaml ;} \
| awk '{ print $2 }' | cut -d - -f 1 | cut -d . -f 1,2,3}
The hardcoded ocaml version was a remnant from llvm-svn and intended to ensure installed ocaml was the same as where llvm-ocaml-svn was build against.
This worked because ocaml was a dependency for llvm-ocaml-svn, but ocaml is an optdepend for llvm-git and optdepends can't have version requirements.
I've removed the hardcocded version requirement.
Yup, ocaml was upgraded in repos and you're the first to notice that breaks building .
I'll update it and/or look into methods to automate getting that version.
error: target not found: ocaml=4.07.1
Is that right? ocaml in extra is on 4.08.0
Hi, thanks alot for the suggestions. I figured out what was wrong on my part. Turns out my buildfolder ran out of space, even though no error pointed to this at first. I moved it around and now it build fine. Sorry :)
I have been building @Lone_Wolf's llvm-git, llvm-minimal-git and lib32 variants in my repo (chaotic-aur) every single day since February, including checks. And all this time I recall it failing only two or three times. The secret is to always build in a clean chroot. (I also build mesa-git hourly, this sometimes fails in the building, but it's usually fixed a few minutes later )
I just finshed building, got lots of warnings, but NO build failures at all with a fully updated archlinux . There were test failures, but those are very common with llvm trunk and skipping them with makepkg --nocheck option is easy.
If you don't use devtools, build with makepkg --cleanbuild --syncdeps --rmdeps .
Make sure no other llvm package is installed. An existing installation of ocaml and python-recommonmark can also cause problems.
Incorrect python installs can break the build() & check() easily. Make sure you're only using python3 from arch repos. If you use pip, conda , anaconda or other stuff that tries to manage python , create a separate user for those or for building llvm-git.
Lordheavy unofficial repo has switched to -git, so the -svn provides can go. packages that still depend on them should be updated (or orphaned if maintainer is unactive). I will add llvm-git to provides and also look at provides as a whole.
This is a deliberate choice, I will add pinned comments explaining the reasoning.
Thanks for testing, nightuser. I have good resuilts with that option in llvm-minimal-git and your confirmation helps. I will switch to that method.
Same issues as cj360. Looking through bugzilla it looked like it's an issue with gcc 9.1, so I downgraded it to 8.3.0. However same results as cj360 just a bit later on.
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.