Arch Linux User Repository

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.

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

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.

I'll see if this allows Clang to run properly.

updated pinned comment

==> Making package: libclc-git 1:r585.9f6204e-1 (Sun Apr 14 11:29:47 2019)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating libclc git repo...
Fetching origin
warning: redirecting to https://git.llvm.org/git/libclc.git/
==> Validating source files with md5sums...
    libclc ... Skipped
==> Extracting sources...
  -> Creating working copy of libclc git repo...
Reset branch 'makepkg'
==> Starting pkgver()...
==> Removing existing $pkgdir/ directory...
==> Starting build()...
LLVM-LINK nvptx--nvidiacl/lib/builtins.link.bc
CXX utils/prepare-builtins.o
LLVM-CC nvptx64--nvidiacl/lib/subnormal_config.cl.bc
LLVM-AS nvptx64--nvidiacl/lib/subnormal_helper_func.ll.bc
Stack dump:
0.      Program arguments: /usr/bin/clang++ -MMD -MF utils/prepare-builtins.o.d -I/usr/include -std=c++11 -fno-exceptions -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -fno-exceptions -fno-rtti -DHAVE_LLVM=0x0900 -c -o utils/prepare-builtins.o ./utils/prepare-builtins.cpp 
1.      Compilation construction
warning: Linking two modules of different data layouts: 'nvptx--nvidiacl/lib/subnormal_helper_func.ll.bc' is '' whereas 'llvm-link' is 'e-p:32:32-i64:64-i128:128-v16:16-v32:32-n16:32:64'

LLVM-CC nvptx64--nvidiacl/lib/async/async_work_group_copy.cl.bc
 #0 0x00007effa79483db llvm::sys::PrintStackTrace(llvm::raw_ostream&) (/usr/bin/../lib/libLLVM-9.so+0xa143db)
 #1 0x00007effa79462c4 llvm::sys::RunSignalHandlers() (/usr/bin/../lib/libLLVM-9.so+0xa122c4)
 #2 0x00007effa794644e (/usr/bin/../lib/libLLVM-9.so+0xa1244e)
 #3 0x00007effa6a93e00 __restore_rt (/usr/bin/../lib/libc.so.6+0x37e00)
 #4 0x000055e4aab7a2d4 std::_Sp_counted_ptr_inplace<llvm::sys::fs::detail::DirIterState, std::allocator<llvm::sys::fs::detail::DirIterState>, (__gnu_cxx::_Lock_policy)2>::_M_get_deleter(std::type_info const&) (/usr/bin/clang+++0x9452d4)
 #5 0x00007effa7901bf6 (/usr/bin/../lib/libLLVM-9.so+0x9cdbf6)
 #6 0x000055e4aac26781 (/usr/bin/clang+++0x9f1781)
 #7 0x000055e4aac27730 (/usr/bin/clang+++0x9f2730)
 #8 0x000055e4aac41486 (/usr/bin/clang+++0xa0c486)
 #9 0x000055e4aab8bf3b clang::driver::Driver::getToolChain(llvm::opt::ArgList const&, llvm::Triple const&) const (/usr/bin/clang+++0x956f3b)
#10 0x000055e4aab97a83 clang::driver::Driver::BuildCompilation(llvm::ArrayRef<char const*>) (/usr/bin/clang+++0x962a83)
#11 0x000055e4aa7d0a17 main (/usr/bin/clang+++0x59ba17)
#12 0x00007effa6a80223 __libc_start_main (/usr/bin/../lib/libc.so.6+0x24223)
#13 0x000055e4aa7e431e _start (/usr/bin/clang+++0x5af31e)
LLVM-CC nvptx64--nvidiacl/lib/async/async_work_group_strided_copy.cl.bc
make: *** [Makefile:9: utils/prepare-builtins.o] Segmentation fault (core dumped)
make: *** Waiting for unfinished jobs....
warning: Linking two modules of different data layouts: 'generic--/lib/subnormal_use_default.bc' is '' whereas 'llvm-link' is 'e-p:32:32-i64:64-i128:128-v16:16-v32:32-n16:32:64'

==> ERROR: A failure occurred in build().
    Aborting...

@Lone_Wolf

some packages still depend on clang-svn/llvm-svn, for example libclc-git

Just in case someone needs, building with a systemd-nspawn container requires some capabilities, or disable tests.

Well, I haven't found the cause of clang breakage, but did find a workaround :

Use llvm-lw-git + compiler-rt-lw-git + clang-lw-git .

Don't bother.

I got the same error even without the patch, before your latest commit.

QuartzDragon : building in clean chroot gives same error.

I'll try building without the enable-SSP-and-PIE-by-default.patch .

• bpierre, was python2 installed during build ? If so, try removing python2 (temporarily) or build in a clean chroot.

• QuartzDragon, I get the same error. I'll check if building in a clean chroot makes a difference.

• I thought llvm-libs-git would no longer conflict with llvm-libs, but it still does. Will check how lordheavy llvm-svn does it.

I'm getting a conflict with the resulting llvm-git package and python2-six:

$ pacman --query --list --file -- llvm-git-9.0.0_r314120.c77bf89dcce-1-x86_64.pkg.tar.gz | grep six.py

llvm-git /usr/lib/python2.7/site-packages/six.py