Package Details: llvm-libs-svn 4.0.0svn_r283448-1

Git Clone URL: (read-only)
Package Base: llvm-svn
Description: The LLVM Compiler Infrastructure (runtime libraries)
Upstream URL:
Keywords: clang llvm
Licenses: custom:University of Illinois
Groups: llvm-toolchain-svn
Conflicts: llvm-libs
Provides: llvm-libs
Replaces: llvm-libs
Submitter: None
Maintainer: kerberizer
Last Packager: kerberizer
Votes: 71
Popularity: 1.515343
First Submitted: 2007-08-02 07:15
Last Updated: 2016-10-06 14:05

Required by (20)

Sources (5)

Pinned Comments

kerberizer commented on 2016-08-11 00:39


Please check the following page for information on:
* possible problems with this package;
* recommendations on how to build it;
* availability of binary packages.

You may also use it for bug reports and pull requests.

Latest Comments

kerberizer commented on 2016-10-06 14:20

[HEADS UP] AMD open source driver users: Upgrade of llvm-libs-svn may corrupt your screen

I'm not sure if this is a genuine issue or some random problem with my specific GPU, but with the last upgrade I've just made, the screen turned into complete mess the moment the LLVM shared lib (I suppose) was upgraded. One could actually see the windows been switched and menus opened, but extremely distorted. It was also a relatively soft issue: logout and login back into Gnome fixed it.

Again, this might not relate to you, but be warned: I suggest upgrading either from the console, or at least without anything else open, so that you can reload the GUI or restart the system without much risk to lose data.

kerberizer commented on 2016-10-06 14:11

[NOTICE] The problem with libLTO being present in both 'llvm-libs-svn' and 'llvm-svn' has been fixed. This pertains as well to lib32-llvm-svn.

kerberizer commented on 2016-10-06 08:09

@yousry, thanks for you comment. Let me see if I got you right: if you build Clang with this PKGBUILD, it segfaults on compiling your game, but if you build it on your own, Clangs compiles your game without problems, right?

I'm afraid I can't spot any differences in how you checkout LLVM et al. compared to the PKGBUILD, except for the obvious lack of libc++ in the latter (it also uses svn export, but this shouldn't matter).

Could you possibly share the full CMake command that you use and what make commands you run afterwards as well, please? Might be more convenient if you file a bug here...

I've already opened an issue myself for the libc++ inclusion. This is a good idea, and I'll see what I can do.

yousry commented on 2016-10-06 06:55

I'm currently trying to create a package for my game: Clang is hereby a necessary part of the toolchain. Unfortunately a build with this version of clang results in a segfault.

I identified several differences to my build process. I use the following package structure:

I use CMAKE (without Ocaml) with ffi and rt enabled.

Please also consider the inclusion of libc++. This could become useful for system independent builds (For example to support BSDs).

kerberizer commented on 2016-10-05 21:11

[NOTICE] There might be currently some problem with the package, where on installation it gives errors like "/usr/lib/ exists in both 'llvm-libs-svn' and 'llvm-svn'". I'll look into this tomorrow.

farseerfc commented on 2016-09-29 03:30

@kerberizer thanks for fixing this

kerberizer commented on 2016-09-28 23:12

[NOTICE] The bug with the OCaml documentation path has been fixed. Thanks again to @farseerfc for reporting this.

If you install the llvm-ocaml-svn package, please have in mind that the HTML documentation now resides in a different place:

old: /usr/share/doc/ocaml/html/
new: /usr/share/doc/llvm/ocaml-html/

On an unrelated note, if anyone is building these packages on i686 (32-bit), I've disabled the LLVM regression tests on that architecture, as they seem to fail often and I'm not quite sure if even upstream cares that much about fixing them. The packages still build fine, and if you'd like so, you may enable the tests by editing the PKGBUILD. Again, this applies only to i686 (32-bit). For x86_64 (64-bit), which I suppose most and likely all of you use, there is no change. Also, this doesn't affect the lib32 compat packages at all.

kerberizer commented on 2016-09-28 18:05

@farseerfc, there's indeed a problem. Guess something changed upstream; I'll see to get it fixed. Thanks for reporting it!

farseerfc commented on 2016-09-28 17:57

build with an error in these 2 days:
mv: cannot stat '/build/llvm-svn/pkg/llvm-svn/usr/share/doc/ocaml': No such file or directory
==> ERROR: A failure occurred in package_llvm-svn().
==> ERROR: Build failed, check /var/lib/archbuild/extra-x86_64/farseerfc/build
How can I fix this problem?

kerberizer commented on 2016-09-05 18:32

[NOTICE] TL;DR: The regression tests should pass fine now.

The problem which @electricprism was facing (and likely everyone else) persists for several days already. Unfortunately, I don't have the time to search for the root cause, but it's a simple matter of not finding the built shared lib when loading the test, so I've committed a simple fix which sets LD_LIBRARY_PATH appropriately while running "make check".

All comments