| Git Clone URL: | https://aur.archlinux.org/llvm-minimal-git.git (read-only, click to copy) |
|---|---|
| Package Base: | llvm-minimal-git |
| Description: | LLVM runtime libraries, trimmed down trunk version |
| Upstream URL: | https://llvm.org/ |
| Licenses: | Apache-2.0 WITH LLVM-exception |
| Submitter: | Lone_Wolf |
| Maintainer: | Lone_Wolf |
| Last Packager: | Lone_Wolf |
| Votes: | 5 |
| Popularity: | 0.000334 |
| First Submitted: | 2019-05-14 19:32 (UTC) |
| Last Updated: | 2025-02-05 00:37 (UTC) |
build the same commit of llvm-git & llvm-minimal-git , then try installing them again.
While pacman will allow it at first, i'd be very surprised if it didn't detect file conflicts and abort before finishing installing .
In case the 3rd pinned comment isn't clear enough
-D LLVM_ENABLE_PROJECTS="polly;lldb;lld;compiler-rt;clang-tools-extra;clang" \
-D LLVM_ENABLE_PROJECTS="clang-tools-extra;clang"
first line is from llvm-git , 2nd from llvm-minmal-git .
Just found out that this package can happily sit installed next to llvm-libs-git.
Don't the two packages provide the same thing?
no，you need install mesa-git and mesa-git's runtime if mesa-git is built with llvm-minimal-git，it will need llvm-libs-minimal-git as dependence
Oh, so mesa-git just need to be build with llvm-minimal-git, but at runtime it works well with stock llvm?
that is a possibilty, but the recommended method is to setup "clean chroot building" to separate runtime & build environments .
See https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot
Got that. So this basically mean that if I want mesa-git on my machine I would probably need to replace the whole llvm suite to avoid issues?
I'll look into moving those files to clang-minimal-git which has a conflict with repo clang so pacman won't allow installing both .
I do think having repo clang & llvm-minimal-git installed together is a bad idea and can cause issues.
Also keep in mind that llvm-libs-minimal-git is the only part needed at runtime and customized to coexist with repo llvm-libs .
Building the packages goes fine, but when I try to install the packages I get the following error:
error: failed to commit transaction (conflicting files)
llvm-minimal-git: /usr/bin/amdgpu-arch exists in filesystem (owned by clang)
llvm-minimal-git: /usr/bin/nvptx-arch exists in filesystem (owned by clang)
llvm-minimal-git: /usr/share/clang-doc/clang-doc-default-stylesheet.css exists in filesystem (owned by clang)
llvm-minimal-git: /usr/share/clang-doc/index.js exists in filesystem (owned by clang)
Errors occurred, no packages were upgraded.
The pkgver at my build is 21.0.0_r526143.077e0c134a31.
built just fine on 14.10, built just fine today - 20.0.0_r515197.37ad65ffb6b8-1
Sounds like you are using customised makepkg.conf/pacman.conf as lld is the llvm linker and clean chroot builds are meant to use gcc & ld .
Also LLVM_ENABLED_SHARED_LIBS=ON is only meant for use by llvm developers in special cases.
Try re-creating the chroot from scratch with $ mkarchroot $CHROOT/root base-devel and only edit the mirrorlist.
Pinned Comments
Lone_Wolf commented on 2022-11-02 11:39 (UTC)
During building you may encounter lots of coredumps, slowing build down or even dramatically reducing the responsiveness of your system.
See https://wiki.archlinux.org/title/Core_dump for solutions/workarounds .
Lone_Wolf commented on 2020-08-22 12:30 (UTC) (edited on 2020-08-22 12:31 (UTC) by Lone_Wolf)
Archlinux currently has 3 llvm git implementations
this package
llvm-git
packages created & maintained by Lordheavy, an arch developer
Lone_Wolf commented on 2019-08-25 12:39 (UTC) (edited on 2021-01-30 21:15 (UTC) by Lone_Wolf)
Why does this package exist ?
Llvm & aur llvm-git are intended to provide a full development environment of llvm/clang suite that can replace eachother completely (aur llvm-git adds some xtra functionality)
llvm-minimal-git is a stripped-down llvm trunk build with these goals :
Some of the things that are stripped out :
Maintainers (and users) should only depend on llvm-miminal-git after verifying it satisfies what they need.
Lone_Wolf commented on 2019-08-21 13:51 (UTC) (edited on 2024-02-24 20:50 (UTC) by Lone_Wolf)
When building this you are likely to see test failures in terminal output / logs.
The command used for the tests has been changed to continue regardless of failures. Incase you don't want to run the tests you can use --nocheck option of makepkg.