Package Details: lib32-llvm-git 19.0.0_r495961.17b86d5978af-1

Git Clone URL: https://aur.archlinux.org/lib32-llvm-git.git (read-only, click to copy)
Package Base: lib32-llvm-git
Description: Collection of modular and reusable compiler and toolchain technologies (32-bit, git)
Upstream URL: https://llvm.org/
Keywords: clang git llvm
Licenses: custom:Apache 2.0 with LLVM Exception
Conflicts: lib32-clang, lib32-llvm
Provides: aur-lib32-llvm-git, lib32-clang, lib32-clang-git, lib32-llvm
Submitter: yurikoles
Maintainer: rjahanbakhshi
Last Packager: rjahanbakhshi
Votes: 12
Popularity: 0.000062
First Submitted: 2019-01-11 15:50 (UTC)
Last Updated: 2024-04-17 08:43 (UTC)

Required by (30)

Sources (1)

Pinned Comments

Latest Comments

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

Enverex commented on 2016-07-13 12:41 (UTC)

Doesn't built here: findlib: [WARNING] Interface llvm.cmi occurs in several directories: /home/arcade/build/pkg-autobuild/lib32-llvm-svn/src/build/bindings/ocaml/llvm, /usr/lib/ocaml findlib: [WARNING] Interface llvm_target.cmi occurs in several directories: /home/arcade/build/pkg-autobuild/lib32-llvm-svn/src/build/bindings/ocaml/target, /usr/lib/ocaml File "/home/arcade/build/pkg-autobuild/lib32-llvm-svn/src/build/bindings/ocaml/executionengine/llvm_executionengine.ml", line 1: Error: The files /usr/lib/ocaml/llvm_target.cmi and llvm_executionengine.cmi make inconsistent assumptions over interface Llvm_target 1 error(s) encountered

kerberizer commented on 2016-02-16 18:16 (UTC)

[HEADS UP] Users of "{lib32-,}llvm-svn", "{lib32-,}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 the open source drivers, * you use "{lib32-,}mesa-git" from AUR, with version < g0bba5ca, * you use "{lib32-,}llvm-svn" from AUR, with version >= r260919, ...then you __must__ recompile the Mesa packages (or possibly upgrade again from the "mesa-git" binary repo you use). The reason is explained in this Mesa commit: https://cgit.freedesktop.org/mesa/mesa/commit/?id=0bba5ca468cdcd1f6f9bb6736c8a75e43fbe0cd5 If Mesa is not recompiled, you'll face errors of the type: libGL: dlopen /usr/lib/xorg/modules/dri/radeonsi_dri.so failed (/usr/lib/xorg/modules/dri/radeonsi_dri.so: undefined symbol: LLVMAddTargetData) Please note that with the AMD open source drivers, recompiling Mesa on every LLVM upgrade is generally a good practice, even though most of the time it will not be strictly necessary.

kerberizer commented on 2016-01-14 10:35 (UTC)

[HEADS UP] Users of `{lib32-,}llvm-svn`, `{lib32-,}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 the 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). The reason is the recent branching of LLVM/Clang 3.8 and bumping the development version to 3.9, which also affects the shared library version. If Mesa is not recompiled, with the new {lib32-,}llvm-svn packages you'll face errors of the type: gbm: Last dlopen error: libLLVM-3.8svn.so: cannot open shared object file: No such file or directory (EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/swrast_dri.so failed (libLLVM-3.8svn.so: cannot open shared object file: No such file or directory) Please note that for the AMD open source drivers, recompiling Mesa on every LLVM upgrade is generally a good practice, even though most of the time it will not be strictly necessary.

kerberizer commented on 2016-01-14 03:41 (UTC)

[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 (UTC)

[NOTICE] The binary repo is back online.

kerberizer commented on 2015-12-10 20:22 (UTC)

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 (UTC)

[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 (UTC)

@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 (UTC)

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

kerberizer commented on 2015-11-05 16:11 (UTC)

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

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