Package Details: clang-analyzer-svn 5.0.0svn_r295214-1

Git Clone URL: (read-only)
Package Base: llvm-svn
Description: Source code analysis tool for Clang, supporting C, C++, and Objective-C
Upstream URL:
Keywords: clang llvm
Licenses: custom:University of Illinois
Groups: llvm-toolchain-svn
Conflicts: clang-analyzer
Provides: clang-analyzer
Replaces: clang-analyzer
Submitter: None
Maintainer: kerberizer
Last Packager: kerberizer
Votes: 72
Popularity: 0.840858
First Submitted: 2007-08-02 07:15
Last Updated: 2017-02-15 19:20

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 2017-02-27 20:00

@WoefulDerelict, thank you very much for the notice! I'm actually fine with either solution, but one obvious benefit if libc++/abi becomes part of this PKGBUILD is that I'll be able to also provide binary packages from the llvm-svn repo that I maintain.

Like it usually happens, the devil is in the details. As discussed on, one important issue is whether to use GCC or Clang -- and which Clang too -- for building the library, which gets further complicated by the nature of the split packages. My experiments so far have shown that each compiler leads to different libcxx unit tests failing: 4 tests were failing with GCC vs 1 with Clang from extra. The second problem is exactly those failing tests. I indeed tend to be a perfectionist, but a failing unit test is usually not a good indication, perfectionist or not. I'd really like to solve or at least have a clear path to solving these issues before merging libc++/abi, and any help with this will be really appreciated.

And speaking about help, I'll also be very grateful if people knowledgeable with YAML take a look at, resp. I've already bisected the problem (at least on Arch), but more eyes and testing are needed to understand why this is (likely) failing only on certain distributions/systems.

Edit: Wrongly referenced the issue rather than the pull request.

WoefulDerelict commented on 2017-02-27 19:02

brunocodutra stopped by libc++ [] asking how I felt about maintaining an -svn variant of the split package. The user also referenced a discussion here:

One is referencing this here to document the forthcoming work to include libc++-svn/libc++abi-svn in this split PKGBUILD transparently in the AUR in order to help prevent the appearance of PKGBUILD(s) that would block inclusion.

streetwalrus commented on 2017-02-17 12:38

Yeah, I'm using this package for mesa-git as well, but I also use Dolphin. Thanks a lot!

kerberizer commented on 2017-02-15 19:34

@streetwalrus, thank you very much for your helpful report. My own use of LLVM is almost exclusively as a Mesa dependency and therefore I really appreciate such feedback. should now be installed by the llvm-libs-svn package.

streetwalrus commented on 2017-02-15 10:51

Building dolphin-emu-git fails with the following error:

CMake Error at /usr/lib/cmake/llvm/LLVMExports.cmake:1158 (message):
The imported target "LLVMHello" references the file


but this file does not exist. Possible reasons include:

* The file was deleted, renamed, or moved to another location.

* An install or uninstall procedure did not complete successfully.

* The installation package was faulty and contained


but not all the files it references.

Call Stack (most recent call first):
/usr/lib64/cmake/llvm/LLVMConfig.cmake:215 (include)
Source/Core/UICommon/CMakeLists.txt:13 (find_package)

Removing references to LLVMHello from /usr/lib/cmake/llvm/LLVMExports-release.cmake solves the problem. This is probably a new file that needs to be installed or left out of the build entirely.
I'm running builds from the repo. The file seems to be present in the package from extra.
Edit: the PKGBUILD from extra doesn't seem to explicitly install this file, maybe it was removed upstream and the cmake files weren't updated.

kerberizer commented on 2016-12-07 17:29

[NOTICE] python2-requests added as a build dependency, otherwise Sphinx fails when generating documentation with "pkg_resources.DistributionNotFound: The 'requests' distribution was not found and is required by Sphinx"

kerberizer commented on 2016-11-10 13:14

[IMPORTANT] Mesa again builds correctly with the latest {,lib32-}llvm-svn, so it's safe to update your LLVM packages.


NB: You might need this tiny patch to mesa-git's PKGBUILD, which I'm sure @Lone_Wolf will apply shortly.

diff --git a/PKGBUILD b/PKGBUILD
index 0a8836e..96d5c8d 100644
@@ -168,7 +168,7 @@ package_mesa-vulkan-radeon-git() {

install -m755 -d ${pkgdir}/usr/share/vulkan/icd.d
- mv -v ${srcdir}/fakeinstall/usr/share/vulkan/icd.d/radeon_icd.json ${pkgdir}/usr/share/vulkan/icd.d/
+ mv -v ${srcdir}/fakeinstall/usr/share/vulkan/icd.d/radeon_icd.*.json ${pkgdir}/usr/share/vulkan/icd.d/

install -m755 -d ${pkgdir}/usr/lib
mv -v ${srcdir}/fakeinstall/usr/lib/ ${pkgdir}/usr/lib/

kerberizer commented on 2016-11-07 19:50

[NOTICE] Update for the LLVM r286062 issue with Mesa is now in code review:

Edit: Updated the link.

kerberizer commented on 2016-11-07 14:45

[HEADS UP] LLVM r286062 breaks Mesa

If you use llvm-svn with Mesa, particularly for the AMD open source driver, DO NOT upgrade LLVM to version >=r286062. Upgrading will not only break the existing driver, but will also prevent you from building Mesa altogether (in both cases there will be error messages related to missing LLVMAddFunctionAttr).

If you have already upgraded to a version >=r286062, here are some possible solutions:
1. Don't restart X: everything should mostly keep running, since the older shared lib has already been loaded in memory. A fix for Mesa should emerge in the meantime, probably in a day or two at most.
2. Return to an older LLVM version: if you don't regularly clear /var/cache/pacman/pkg, you should be able to find there package versions earlier than r286062.
3. Switch to llvm/mesa from the official repositories. This may be somewhat tricky, depending on what exact packages you had installed. Try replacing as much as possible of the installed llvm-svn/mesa-git packages with their llvm/mesa counterparts. Remove the -svn/-git packages that don't have an equivalent 'provides' in the official repos. Of course, this might break some functionality for you.

I'll also consider keeping older versions of the llvm-svn* packages in the binary repo as a backup.


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.

All comments