@mtahmed
Pull request done to your github repo.
Argh wait, they just commited r196787 with another bug:
no ‘lldb_private::Error ProcessLinux::DoResume()’ member function declared in class ‘ProcessLinux’
I will look into it.
Maybe PKGBUILD should be changed to checkout a revision that we know is building without error.
Search Criteria
Package Base Details: llvm-git
Package Actions
Git Clone URL: | https://aur.archlinux.org/llvm-git.git (read-only, click to copy) |
---|---|
Keywords: | clang git lld lldb llvm polly |
Submitter: | yurikoles |
Maintainer: | rjahanbakhshi |
Last Packager: | rjahanbakhshi |
Votes: | 118 |
Popularity: | 1.36 |
First Submitted: | 2018-12-05 13:56 (UTC) |
Last Updated: | 2023-10-30 08:09 (UTC) |
Packages (3)
Latest Comments
« First ‹ Previous 1 .. 53 54 55 56 57 58 59 60 61 62 63 .. 69 Next › Last »
xdegaye commented on 2013-12-09 17:27 (UTC)
xdegaye commented on 2013-12-08 23:45 (UTC)
@mtahmed
No problem, I will do as you suggest, it is indeed much more efficient.
I did make sure to write these codepads with unix LFs, so it must be
codepad that have mapped them to CRLFs, probably because I flagged them
as Language 'Text', should have used 'C' instead.
mtahmed commented on 2013-12-08 23:22 (UTC)
@xdegaye
Thanks a lot for taking the time to patch this. I am however very (very) busy these days and although writing this message also takes time, it's worth it since you are a regular contributor. Could you please instead send a pull request to the github repo where I am maintain this (https://github.com/mtahmed/aur)? It's also probably easier for you to contribute patches as well after the first time.
I have to download the files, convert them (dos2unix), manually generate diffs to see the changes, package it and then update the this AUR.
I would really appreciate if you could do that instead (and use Unix line terminators :) ... not sure if it's codepad that adds the dos line terminators). Thanks!
xdegaye commented on 2013-12-08 23:02 (UTC)
Build fails on the current lldb svn head. The following mails to upstream list the problems and
propose two patches:
http://thread.gmane.org/gmane.comp.debugging.lldb.devel/2792
http://thread.gmane.org/gmane.comp.debugging.lldb.devel/2793
http://thread.gmane.org/gmane.comp.debugging.lldb.devel/2794
PKGBUILD at http://codepad.org/bWHG8EkT fixes temporarily the problems with
sin_len.patch at http://codepad.org/zAr2beuT and usr_bin_env_python.patch
at http://codepad.org/Eurthufy.
This PKGBUILD can be used while waiting for upstream to fix the two bugs.
In any case, the '-DLLVM_ENABLE_CXX11=ON' cmake variable is needed now.
Krejzi commented on 2013-12-08 17:42 (UTC)
Please sync with llvm from [extra] and, if possible, add necessarry files required to have lib32-llvm-svn, which are also available in [extra].
justinzane commented on 2013-11-27 06:03 (UTC)
This is the tools/gold/README:
This directory contains a plugin that is designed to work with binutils
gold linker. At present time, this is not the default linker in
binutils, and the default build of gold does not support plugins.
Obtaining binutils:
cvs -z 9 -d :pserver:anoncvs@sourceware.org:/cvs/src login
{enter "anoncvs" as the password}
cvs -z 9 -d :pserver:anoncvs@sourceware.org:/cvs/src co binutils
This will create a src/ directory. Make a build/ directory and from
there configure binutils with "../src/configure --enable-gold --enable-plugins".
Then build binutils with "make all-gold".
To build the LLVMgold plugin, configure LLVM with the option
--with-binutils-include=/path/to/binutils/src/include/ --enable-pic. To use the
plugin, run "ld-new --plugin /path/to/LLVMgold.so".
Without PIC libLTO and LLVMgold are not being built (because they would fail
link on x86-64 with a relocation error: PIC and non-PIC can't be combined).
As an alternative to passing --enable-pic, you can use 'make ENABLE_PIC=1' in
your entire LLVM build.
How on earth to I edit the PKGBUILD for this?
justinzane commented on 2013-11-27 06:00 (UTC)
LLVMgold.so, the linker plugin seems to have disappeared after replacing the repo clang with this; which breaks a number of my builds. How to recover it?
xdegaye commented on 2013-11-12 17:00 (UTC)
@ aksr
lldb also crashes on my VmWare VM, see
http://llvm.org/bugs/show_bug.cgi?id=17802
You could check if you have the same backtrace of the crash, either running lldb
from gdb or examining the core file with gdb.
To disable the handling of core dumps by systemd-coredumpctl(1), see
https://wiki.archlinux.org/index.php/Systemd#Disabling_application_crash_dumps_journaling
aksr commented on 2013-11-12 09:14 (UTC)
No, something else is missing. I reinstalled everything, still, the same problem persists.
Pinned Comments
Lone_Wolf commented on 2021-08-16 11:26 (UTC)
When you have this package installed applications that are built against repo-llvm/clang WILL fail unless they are rebuild against this package.
This includes QTCreator, kdevelop , mesa, intel-compute-runtime, gnome-builder to name a few.
Lone_Wolf commented on 2020-08-22 12:18 (UTC) (edited on 2021-02-06 12:51 (UTC) by Lone_Wolf)
Archlinux currently has 3 llvm git implementations
This package
llvm-minimal-git
packages created & maintained by Lordheavy, an arch developer
Lone_Wolf commented on 2019-04-12 20:41 (UTC) (edited on 2019-12-16 22:45 (UTC) by Lone_Wolf)
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.
llvm-git
The 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.
The check() function fails rather often, but I do suggest to build with them. If build fails due to test failure you can add --nocheck to skip the tests.