Package Base Details: llvm-git

Git Clone URL: https://aur.archlinux.org/llvm-git.git (read-only, click to copy)
Keywords: clang git lld lldb llvm polly
Submitter: yurikoles
Maintainer: Lone_Wolf
Last Packager: Lone_Wolf
Votes: 111
Popularity: 0.090108
First Submitted: 2018-12-05 13:56
Last Updated: 2020-06-08 18:03

Pinned Comments

Lone_Wolf commented on 2019-04-12 20:41

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

« First ‹ Previous ... 7 8 9 10 11 12 13 14 15 16 17 ... Next › Last »

yurikoles commented on 2019-03-29 14:48

@PedroHLC thanks for report, I already fixed some errors while building in clean chroot. But I still can't find what else missing. Help is appreciated.

PedroHLC commented on 2019-03-29 14:15

@yurikoles, this is a log from a clean chroot building, I'm getting a lot of repetitive warnings, some erros with missing binaries and then it fails: https://lonewolf.pedrohlc.com/chaotic-aur/makepkglogs/_experiments/llvm-git.log Seems like there're a few missing dependencies, could you take a look?

cdkitching commented on 2019-03-29 05:23

Since the Arch bug that motivated me to make this package in the first place was fixed years ago, I no longer care.

Anyone who wants to take it on is welcome to do so.

yurikoles commented on 2019-03-18 12:07

@zor1984qq

This is known issue, I had updated pinned message.

P.S. Сергей, я то знаю русский, но на будущее, не забывайте про export LC_ALL=C перед выполнением команды, с которой у вас проблема.

zor1984qq commented on 2019-03-18 11:07

[ 18%] Linking CXX static library ../../libLLVMDebugInfoPDB.a [ 18%] Built target LLVMDebugInfoPDB make: *** [Makefile:152: all] Ошибка 2 ==> ОШИБКА: Произошел сбой в build(). Прерывание... 2019-03-18 13:59:12,373 - wrappers - makepkg - ERROR - makepkg query ['makepkg', '-cf', '--noconfirm'] failed in directory /home/sergey/.cache/aurman/llvm-git

BillFleming commented on 2019-03-07 11:03

Please add python-recommonmark to dependencies.

kerberizer commented on 2019-02-18 23:19

Just to let you know, guys, that I'm slowly making some progress. It's not a tremendous amount of work actually, but unfortunately I rarely have the necessary time to focus on it and I also want to make sure it will work reasonably well. I really appreciate your patience and understanding. I guess that in the meantime those who build the packages on their own already use some workarounds, and for those who wait for the binary repos, I really hope that in the next few days I'll be ready (but, please, take this with a grain of salt too).

sleepprogger commented on 2019-02-02 18:58

@PedroHLC:

It looks like some files moved. This is prob not the correct way to go but changing that line to

mv -f "${srcdir}"/build/lib/{BugpointPasses,LLVMgold,LLVMHello}.so "${srcdir}/"

and adding a rm -f "${pkgdir}"/usr/lib/LLVMgold.so

to prevent LLVMgold.so to be in both llvm-libs and llvm solved the problem for me. `

kerberizer commented on 2019-02-01 16:47

@clap22, I'm very sorry for not paying enough attention to these packages and the repo lately. I've been through some major changes in my day job that really consumed all my time. But I'm not abandoning the packages. As always, some help or even a new maintainer with more free time (and perhaps more expertise) will be welcome, but I'll continue doing whatever I can to keep them and the repo alive and current.

Anyhow, I started working on switching the packages to Ninja, which is what, apparently, nowadays most LLVM devs use. There are some problems that I need to deal with though—I don't think they are serious, but can't tell yet how much time I'll need (FWIW, llvm in extra has been using Ninja fine for some time).

Something else that I'm considering—and which we've discussed with @Lone_Wolf some time ago—is splitting clang into its own package (or pkgbase). I'm mentioning this because it might turn out to be best done together with the Ninja switch. If it can wait, though, I won't bother with it for now.

Finally, some of you are perhaps aware that LLVM is in the process of transition from Subversion to Git for its source code. Once it gets finalized we'll need to switch to Git, and the obvious question is what's going to happen to the package names: keep them (it really doesn't matter what VCS is used in the package), or rename/move to -git names. I'll probably ask in aur-general@ what's considered best practice in such cases, but if somebody here already knows, please do comment.

clap22 commented on 2019-02-01 02:58

I miss your binaries, are you abandoning them?