Package Base Details: lib32-llvm-git

Git Clone URL: https://aur.archlinux.org/lib32-llvm-git.git (read-only)
Keywords: clang git llvm
Submitter: yurikoles
Maintainer: Lone_Wolf
Last Packager: Lone_Wolf
Votes: 11
Popularity: 0.057836
First Submitted: 2019-01-11 15:50
Last Updated: 2019-11-14 12:52

Latest Comments

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

kerberizer commented on 2016-01-14 03:41

[NOTICE] Future release 3.8 has been branched a few hours ago, so welcome to LLVM/Clang 3.9! ;)

kerberizer commented on 2015-12-11 15:21

[NOTICE] The binary repo is back online.

kerberizer commented on 2015-12-10 20:22

I'm afraid the binary repo will be down for longer than I expected. I'll let you know once it's back on-line. Again, I'm really sorry for this inconvenience.

kerberizer commented on 2015-12-09 22:13

[NOTICE] Due to upstream link problems, the binary repo is currently unavailable. Unfortunately, at the moment no estimate on the time needed to fix the links can be given, but I expect the problem to be solved not later than 24 hours from now. Sorry for the inconvenience.

kerberizer commented on 2015-11-27 13:46

@yurikoles, I'm not sure I understand what the problem is. In what sense does it try to build single package?

If you mean this...

==> Building and installing package
==> This PKGBUILD provides " lib32-llvm-svn lib32-llvm-libs-svn lib32-clang-svn "
==> Install only lib32-llvm-svn ? [Y/n]

...then it should be answered "no".

And, in general, I think yaourt is not the best way to install such complex tools, not to mention that the good practice is building in a clean chroot.

yurikoles commented on 2015-11-27 04:02

I'm unable to install this pacage with yaourt, as it tries to build single package.

kerberizer commented on 2015-11-05 16:11

Also, please note that the libLTO.so version symlinks are not installed any more.

kerberizer commented on 2015-11-05 15:51

[NOTICE] The PKGBUILD has been updated to reflect the changes from r251411 and r252093 in upstream. Using an old PKGBUILD will lead to errors like this:

error: failed to commit transaction (conflicting files)
/usr/lib32/libLLVM-3.8svn.so exists in both 'lib32-llvm-libs-svn' and 'lib32-llvm-svn'

kerberizer commented on 2015-10-10 16:13

[NOTICE] Shared library fixed

The critical bug with LLVM not exporting the expected symbols seems to have been fixed completely upstream, so I've removed the last custom patch. Keep this in mind if you notice any "undefined reference" errors.

References:
* https://github.com/kerberizer/llvm-svn/issues/2
* https://llvm.org/bugs/show_bug.cgi?id=24157
* http://llvm.org/viewvc/llvm-project/llvm/trunk/tools/llvm-shlib/CMakeLists.txt?r1=246918&r2=249862&diff_format=h

kerberizer commented on 2015-10-09 11:10

[HEADS UP] Users of `llvm-svn`, `mesa-git` and AMD video cards MUST recompile Mesa

If ALL of the following are true for you:
* you use an AMD video card with open source drivers,
* you use `{lib32-,}mesa-git` from AUR,
* you use `{lib32-,}llvm-svn` from AUR,
* you have upgraded the `{lib32-,}llvm-svn` packages during the last ~24 hours, whether by compiling yourself or from the `llvm-svn` binary repo,
then please note that you MUST recompile the Mesa packages (or possibly upgrade again from the `mesa-git` binary repo you use) due to a recent change in the LLVM shared library.

If Mesa is not recompiled, with the new llvm-svn packages you'll most likely face errors like this:

gbm: Last dlopen error: /usr/lib/xorg/modules/dri/radeonsi_dri.so: undefined symbol: _ZN4llvm21SymbolTableListTraitsINS_11InstructionENS_10BasicBlockEE13addNodeToListEPS1_

Please note that for the AMD open source drivers recompiling Mesa on every LLVM upgrade is a good practice, even though most of the time it might not be strictly necessary.