@nstgc Actually I just tried it with removing python-yaml
first and it still failed with two tests:
Failing Tests (2):
LLVM :: tools/gold/X86/thinlto_weak_library.ll
LLVM :: tools/gold/X86/v1.16/wrap-2.ll
Git Clone URL: | https://aur.archlinux.org/llvm-git.git (read-only, click to copy) |
---|---|
Package Base: | llvm-git |
Description: | runtime libraries for llvm-git |
Upstream URL: | https://llvm.org/ |
Keywords: | clang git lld lldb llvm polly |
Licenses: | custom:Apache 2.0 with LLVM Exception |
Conflicts: | llvm-libs |
Provides: | aur-llvm-libs-git, llvm-libs |
Submitter: | yurikoles |
Maintainer: | rjahanbakhshi |
Last Packager: | rjahanbakhshi |
Votes: | 118 |
Popularity: | 0.005682 |
First Submitted: | 2018-12-05 13:56 (UTC) |
Last Updated: | 2024-04-17 08:17 (UTC) |
« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 .. 70 Next › Last »
@nstgc Actually I just tried it with removing python-yaml
first and it still failed with two tests:
Failing Tests (2):
LLVM :: tools/gold/X86/thinlto_weak_library.ll
LLVM :: tools/gold/X86/v1.16/wrap-2.ll
@gardotd426 This is just my two cents as a two bit user, but I don't see why it's worth taking chances when you can easily run pacman -Rdd python-yaml
and then reinstall it after compiling is down. You could even make it a one liner:
sudo pacman -Rdd python-yaml && makepkg -sir && sudo pacman -S --noconfirm python-yaml
Assuming you didn't delete the package archive, that shouldn't take long.
So does python-yaml need to be removed before this will properly work, or is it enough to just use --nocheck
?
@Lone_Wolf Thanks for that! python-yaml is required by lutris, but I can uninstall that long enough to build this. And I will take your advise and build llvm-minimum-git instead. It has this same issue by the way.
I've confirmed the test failure occurs only with python-yaml present and reported the bug.
Yup, those are the log files I needed.
File "/home/nstgc5/Installers/llvm-git.aur/src/llvm-project/llvm/tools/opt-viewer/opt-viewer.py", line 200, in render_entry
escaped_name = cgi.escape(r.DemangledFunctionName)
AttributeError: module 'cgi' has no attribute 'escape'
cgi.escape was removed in python 3.8, so the error itself is correct. Not sure why llvm tools want to use deprecated functionality.
The log also mentions you have python module yaml , and yaml is not present in my build environment .
@Lone_Worlf These are the logs I think you are looking for:
https://gist.github.com/nstgc/34b6824016e861a0e310656793a7828c
https://gist.github.com/nstgc/ea881f98eeec5c4cc8db704f5bb1f218
@Lone_Wolf A question (sorry). I was reading through the stickies for llvm-minimal-git and it mentioned errors for non-amdgpu (and to ignore them). I'm building llvm (and mesa) ahead of installing a new video. Should I wait until I have the AMD card in my computer before compiling this stuff? I've never compiled drivers or kernels before so I'm not really sure of best practices.
@Lone_Wolf This is embarrassing, but I've never really gone to this extent to get something in the AUR installed so I don't know what you mean by "log files". Reading through man makepkg
I'm guessing you mean for me to use the -L
switch like, LOGDEST=$PWD/logs makepkg -sirL
? This?
lldb tests re-enabled.
While looking at lldb cmakelists.txt for options to solve the test failure, I noticed an option to use system-provided python-six . Using that option allowed to remove a workaround from the package_llvm-git() function.
nstgc : post log files of the build somewhere. I'll run a clean chroot build to verify dependencies.
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.