Package Details: llvm-git 16.0.0_r439853.1fe096ef59d1-1

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: 116
Popularity: 0.015328
First Submitted: 2018-12-05 13:56 (UTC)
Last Updated: 2022-10-25 22:15 (UTC)

Required by (1779)

Sources (2)

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

  1. This package

    • It aims to provide a full llvm/clang compiler environment for development purposes.
    • Supports cross-compiling , bindings for external stuff (python, ocaml etc) , and some things not in extra-llvm.
    • intended to be used with archlinux core,extra & community repos
    • CONFLICTS with extra llvm/clang packages
    • Currently there's no repo with binary versions
  2. llvm-minimal-git

    • focuses on providing stuff needed for AUR mesa-git. Doesn't support cross-compiling or any bindings for external stuff like ocaml & python.
    • intended to be used with archlinux core,extra & community repos
    • compatible with extra llvm/clang packages
    • no repo with binary versions
  3. packages created & maintained by Lordheavy, an arch developer

    • intended to be used with archlinux testing repos
    • sometimes has problems on systems where testing repos are disabled
    • uses same package structure as llvm/clang in official repos
    • source
    • binary versions in LordHeavys unoffical repo

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.

    It conflicts with the repo llvm-libs package. This is the only way to make sure the llvm linker from git is used, and that's needed for a full dev environment.

  • llvm-git

    has llvm , clang, compiler-rt, ocaml & python bindings, polly , lld , lldb .


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.

# Add to makepkg.conf
# limit ninja to 20 jobs
# requires special code in PKGBUILD
# see ninja --help for additonal options
NINJAFLAGS="-j20"

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.

Latest Comments

1 2 3 4 5 6 .. 67 Next › Last »

soloturn commented on 2023-02-08 04:20 (UTC)

we now have flags for the repo cloning which saves quite some bandwith:

GITFLAGS="--filter=tree:0" makepkg
GITFLAGS="--depth=1" makepkg
GITFLAGS="--depth=1" paru -S linux-mainline

--depth works with all repositories, --filter in case the repo supports partial clones. it even updates the repo correctly as soon as this is merged: https://gitlab.archlinux.org/pacman/pacman/-/merge_requests/53

if you give it a try and make a comment into the pull request if something does not work i'd be glad.

ivanmlerner commented on 2023-01-29 17:01 (UTC) (edited on 2023-01-30 23:17 (UTC) by ivanmlerner)

@rjahanbakhshi, thanks, I was able to build it in a clean chroot like you said. I don't know if it is still necessary, but I am using an up-to-date arch linux, with mesa-git AUR package, and somehow only noticed now the recommendation to use llvm from AUR. I also have opencl-amd installed, and that seems to have files related to hsa.

rjahanbakhshi commented on 2023-01-27 00:11 (UTC)

@ivanmlerner,

I don't see any errors in building this package in a clean chroot environment. Can you share some details about your environment and the commands you're using to build this?

ivanmlerner commented on 2023-01-22 23:44 (UTC) (edited on 2023-01-22 23:46 (UTC) by ivanmlerner)

Hello, I am getting these errors when trying to build the package:

[7106/8254] Building CXX object tools/clang/tools/amdgpu-arch/CMakeFiles/amdgpu-arch.dir/AMDGPUArch.cpp.o
FAILED: tools/clang/tools/amdgpu-arch/CMakeFiles/amdgpu-arch.dir/AMDGPUArch.cpp.o 
/usr/bin/c++ -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/home/**/llvm-git/src/_build/tools/clang/tools/amdgpu-arch -I/home/**/llvm-git/src/llvm-project/clang/tools/amdgpu-arch -I/home/**/llvm-git/src/llvm-project/clang/include -I/home/**/llvm-git/src/_build/tools/clang/include -I/home/**/llvm-git/src/_build/include -I/home/**/llvm-git/src/llvm-project/llvm/include -march=znver2 -mtune=znver2 -O2 -pipe -fno-plt -fexceptions         -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security         -fstack-clash-protection -fcf-protection -Wp,-D_GLIBCXX_ASSERTIONS -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move -Wno-pessimizing-move -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment -Wno-misleading-indentation -Wctad-maybe-unsupported -fdiagnostics-color -ffunction-sections -fdata-sections -fno-common -Woverloaded-virtual -fno-strict-aliasing -O3 -DNDEBUG  -fno-exceptions -std=c++17 -MD -MT tools/clang/tools/amdgpu-arch/CMakeFiles/amdgpu-arch.dir/AMDGPUArch.cpp.o -MF tools/clang/tools/amdgpu-arch/CMakeFiles/amdgpu-arch.dir/AMDGPUArch.cpp.o.d -o tools/clang/tools/amdgpu-arch/CMakeFiles/amdgpu-arch.dir/AMDGPUArch.cpp.o -c /home/**/llvm-git/src/llvm-project/clang/tools/amdgpu-arch/AMDGPUArch.cpp
/home/**/llvm-git/src/llvm-project/clang/tools/amdgpu-arch/AMDGPUArch.cpp:84:8: error: ‘hsa_status_t’ does not name a type
   84 | static hsa_status_t iterateAgentsCallback(hsa_agent_t Agent, void *Data) {

/home/**/llvm-git/src/llvm-project/clang/tools/amdgpu-arch/AMDGPUArch.cpp: In function ‘int main(int, char**)’:
/home/**/llvm-git/src/llvm-project/clang/tools/amdgpu-arch/AMDGPUArch.cpp:112:3: error: ‘hsa_status_t’ was not declared in this scope
  112 |   hsa_status_t Status = hsa_init();

/home/**/llvm-git/src/llvm-project/clang/tools/amdgpu-arch/AMDGPUArch.cpp:113:7: error: ‘Status’ was not declared in this scope
  113 |   if (Status != HSA_STATUS_SUCCESS) {

/home/**/llvm-git/src/llvm-project/clang/tools/amdgpu-arch/AMDGPUArch.cpp:113:17: error: ‘HSA_STATUS_SUCCESS’ was not declared in this scope
  113 |   if (Status != HSA_STATUS_SUCCESS) {

/home/**/llvm-git/src/llvm-project/clang/tools/amdgpu-arch/AMDGPUArch.cpp:118:3: error: ‘Status’ was not declared in this scope
  118 |   Status = hsa_iterate_agents(iterateAgentsCallback, &GPUs);

/home/**/llvm-git/src/llvm-project/clang/tools/amdgpu-arch/AMDGPUArch.cpp:118:31: error: ‘iterateAgentsCallback’ was not declared in this scope
  118 |   Status = hsa_iterate_agents(iterateAgentsCallback, &GPUs);

/home/**/llvm-git/src/llvm-project/clang/tools/amdgpu-arch/AMDGPUArch.cpp:118:12: error: ‘hsa_iterate_agents’ was not declared in this scope
  118 |   Status = hsa_iterate_agents(iterateAgentsCallback, &GPUs);

/home/**/llvm-git/src/llvm-project/clang/tools/amdgpu-arch/AMDGPUArch.cpp:119:17: error: ‘HSA_STATUS_SUCCESS’ was not declared in this scope
  119 |   if (Status != HSA_STATUS_SUCCESS) {

/home/**/llvm-git/src/llvm-project/clang/tools/amdgpu-arch/AMDGPUArch.cpp:129:3: error: ‘hsa_shut_down’ was not declared in this scope
  129 |   hsa_shut_down();

Lone_Wolf commented on 2022-12-23 18:01 (UTC)

BTW_IUseGentoo :

lldb is in makedepends array of the llvm-git PKGBUILD, so the build should indeed fail if it's not present .

The lldb package is in archlinux [extra] repo, just install it before building starts. (it can be removed again after building has finished)

BTW_IUseGentoo commented on 2022-12-23 15:43 (UTC)

I needed lldb

==> Missing dependencies:
  -> lldb
==> ERROR: Could not resolve all dependencies.
error: failed to build 'llvm-git-16.0.0_r439853.1fe096ef59d1-1 (llvm-libs-git llvm-git)': 
error: packages failed to build: llvm-git-16.0.0_r439853.1fe096ef59d1-1 (llvm-libs-git llvm-git)

Lone_Wolf commented on 2022-11-30 14:46 (UTC)

Understood, you have thought about this and how you want to use it.

Atleast mesa trunk has used this method years ago, but stopped doing it because no other packages made use of it . I have no objections to adding $pkgver-$pkgrel values in llvm-git .

Keep in mind llvm-git follows upstream default branch, so will switch from 16 to 17 when upstream branches off stable 16 .

You may want to use something like 'llvm>=16' 'llvm<17' to ensure users can switch to stable 16 once it arrives.

alerque commented on 2022-11-29 06:03 (UTC)

@Lone_Wolf I understand what you are saying about so names and versions and agree it would be nice if this package added provides for the sonames with version data so other packages could add that as a run time dependency with proper heads-up when a rebuild was needed. However I think you're wrong about my suggestion being a failure: there is no harm in adding the package version information to the provides like like I showed. It does not solve the same problem as providing the soname, but it does solve a different problem. It allows this package to be used as a makedepends with version information for packages that require to be built against a minimum version newer than what is in [community] at this point. It won't provide a run-time way to keep the soname version matched, but it does provide a build time dependency that is flexible enough to be supplied by this or another future update to the stable package(s).

Lone_Wolf commented on 2022-11-28 12:01 (UTC)

alerque, doing it that way will fail at runtime as packages aren't linked to external libraries using package versions but through sonames .

the command find-libprovides from devtools package can help to make those visible.

$ find-libprovides --ignore-internal llvm-git-16.0.0_r443217.0b74cb42312b-1-x86_64.pkg.tar.zst 
libclang.so=16-64
libclang-cpp.so=16-64
liblldb.so=16-64
liblldbIntelFeatures.so=16-64
$ find-libprovides --ignore-internal llvm-libs-git-16.0.0_r443217.0b74cb42312b-1-x86_64.pkg.tar.zst 
libLTO.so=16-64
libRemarks.so=16-64
$ find-libprovides --ignore-internal llvm-ocaml-git-16.0.0_r443217.0b74cb42312b-1-x86_64.pkg.tar.zst 
bsdtar: *.so*: Not found in archive
bsdtar: Error exit delayed from previous errors.
$ 

If you run the same command on other archlinux (binary) llvm pacakges, you'll get similar results.

If this package adds those sonames to provides, applications can depend on an exact version of the shared library, get a warning when sonames change and a rebuild is necessary.