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: 110
Popularity: 0.026359
First Submitted: 2018-12-05 13:56
Last Updated: 2020-01-09 22:11

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 ... 2 3 4 5 6 7 8 9 10 11 12 ... Next › Last »

Lone_Wolf commented on 2019-04-13 13:31

QuartzDragon : building in clean chroot gives same error.

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

Lone_Wolf commented on 2019-04-13 10:32

  • 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.

bpierre commented on 2019-04-13 09:56

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

QuartzDragon commented on 2019-04-13 08:58

Clang is still borked here... :/

https://invent.kde.org/snippets/153

yurikoles commented on 2019-04-13 08:42

@Lone_Wolf, thanks!

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.

Lone_Wolf commented on 2019-04-09 09:24

Well, this is unexpected and a bit awkward.

A few days ago I started my own llvm development packages.

Then llvm-svn was merged into llvm-git, lib32-llvm-svn into lib32-llvm-git . I was already co-maintainer of llvm-git , made co-maintainer of lib32-llvm-git. Yurikoles orphaned those packages and aur server interface promoted me to maintainer .

So now i'm maintainer of 2 sets of llvm dev packages.

I do think there's room for 2 implementations: my personal one in llvm-lw-git and this package as a continuation of llvm-svn that builds everything. It does need several sub-pacakges but they'll stay in the same pkgbuild.

I dislike the non-copyleft nature of llvm license and my personal use of llvm trunk is limited to mesa-git.

I will keep maintainership of this package for atleast a few weeks, but would prefer if someone who actually uses llvm/clang to compile stuff takes over.

Kerberizer : thanks for all the work you put in llvm-svn. please stay involved with it.

Yurikoles : thank you for stepping up and starting this pacakge when llvm-svn was broken.

The pinned comments will stay as-is for now as a sort of tribute.

Lone_Wolf

QuartzDragon commented on 2019-04-09 07:14

Is Clang borked for anyone else?

Attempting to run it with this package results in this lovely segfault:

https://invent.kde.org/snippets/133

Lone_Wolf commented on 2019-04-06 15:41

I have used this package and bearoso' work as well as yurikoles llvm-git to create new packages . I've uploaded the ones needed for mesa-git and will look into others (lld, lldb, polly) later.

You can find them here :

https://aur.archlinux.org/pkgbase/llvm-lw-git/

https://aur.archlinux.org/pkgbase/compiler-rt-lw-git/

https://aur.archlinux.org/pkgbase/clang-lw-git/

https://aur.archlinux.org/pkgbase/lib32-llvm-lw-git/

Please test them and comment.

Lone_Wolf commented on 2019-04-06 14:13

Please re-enable tests and add a check function .

Incase tests fails, makepkg has a very useful option : --nocheck .