Package Base Details: llvm-git

Git Clone URL: (read-only)
Keywords: clang git lld lldb llvm polly
Submitter: yurikoles
Maintainer: Lone_Wolf
Last Packager: Lone_Wolf
Votes: 110
Popularity: 0.064988
First Submitted: 2018-12-05 13:56
Last Updated: 2019-11-18 14:13

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. I understand how older llvm libs repo packages do it, not sure yet if i agree with the approach.

  • llvm-git

    has llvm , clang, compiler-rt, ocaml & python bindings, polly , lld , lldb . The provides for llvm-svn have been re-added to allow others maintainers to update their packages.

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

llvm check now works, clang check however fails. I suggest to test without nocheck first, if build fails due to test failure add--nocheck .

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 ... Next › Last »

gally commented on 2019-07-10 13:37

Same issues as cj360. Looking through bugzilla it looked like it's an issue with gcc 9.1, so I downgraded it to 8.3.0. However same results as cj360 just a bit later on.

Lone_Wolf commented on 2019-07-04 07:12

The version number suggest that version is from before june 28, or about a week old. Have you tried with latest version from LH repo ?

Does the issue also happen with latest version of this package and is there a llvm bug report ?

Haxk20 commented on 2019-07-03 14:48

After long time not playing Elite Dangerous i launched it but all the shadows were white to my suprise. I got the issue pointed to LLVM. Last known build version from mesa-git repo is r319790.e8da65c698e.

nightuser commented on 2019-06-24 08:15

I tried building with LLVM_ENABLE_PROJECTS instead of moving directories around and it seemed ok. I didn't compare the two options of building the package since it takes ages to compile on my hardware.

QuartzDragon commented on 2019-06-15 11:58

Hey @Lone_Wolf, can you add llvm and llvm-git to the provides?

Every package depending on llvm wants to install llvm from the main repos, which prompted me to look. Adding llvm to provides shut them up. Adding llvm-git also wouldn't be a bad idea, just in-case some other AUR package demands a specific version for whatever random reason.

Griever commented on 2019-06-07 18:30

The provides are really starting to become a bit of a mess and maintenance burden. There's been, like, half a dozen switches on mesa-git?

Is there a reason mesa-git should depend on anything other than regular llvm provides? If so, is there really a reason to depend on anything other than *-git provides? AFAIK, mesa usually maintains compatibility with the last two stable LLVM releases.

Ideally, I believe this should only provide regular llvm, *-git and *-svn for compatibility with outdated packages such as libclc-git. Packages should never explicitly depend on *-git or unique packages unless they actually require it.

I truly appreciate you maintaining these packages, but it's becoming a pain to follow all of the changes and regular PKGBUILD breaks due to makedepend/provide changes. Apologies if there are legitimate reasons why all of this is required and can't be worked around any better.

yurikoles commented on 2019-06-02 20:40

@cj360 but you post it here instead of official LLVM bugzilla?

cj360 commented on 2019-06-02 20:34

Trying to build this package is failing for me with this hardware, Ryzen 1600 16gb ram. Here's some of the output the following

Lone_Wolf commented on 2019-05-26 13:38

jpapadopoulos, this package is supposed to be built aginst python 3.

It does seem when both python2 & python3 are installed cmake uses python2 .

Add -D PYTHON_EXECUTABLE=/usr/bin/python \ to the cmake command and cmake will have to use python3 on archlinux.

I'll do the same in next version of the package.

jpapadopoulos commented on 2019-05-26 08:19

I had the following conflict: llvm-git: /usr/lib/python2.7/site-packages/ exists in filesystem (owned by python2-six) I fixed it editing the PKGBUILD to also remove the 2.7 version of . Maybe this should always be removed and the python2-six added as a dep?