Correct.
I have a dynamic fix for this applied to llvm-minimal-git that will prevent this from happening again.
Update will happen soon.
Git Clone URL: | https://aur.archlinux.org/lib32-llvm-minimal-git.git (read-only, click to copy) |
---|---|
Package Base: | lib32-llvm-minimal-git |
Description: | C language family frontend for LLVM , 32-bit trunk version |
Upstream URL: | http://llvm.org/ |
Licenses: | Apache-2.0 WITH LLVM-exception |
Conflicts: | lib32-clang |
Provides: | lib32-clang |
Submitter: | Lone_Wolf |
Maintainer: | Lone_Wolf |
Last Packager: | Lone_Wolf |
Votes: | 1 |
Popularity: | 0.000000 |
First Submitted: | 2019-05-14 19:33 (UTC) |
Last Updated: | 2024-09-07 18:16 (UTC) |
Correct.
I have a dynamic fix for this applied to llvm-minimal-git that will prevent this from happening again.
Update will happen soon.
Currently getting this:
mv: cannot stat '/tmp/makepkg/lib32-llvm-minimal-git/pkg/lib32-llvm-minimal-git/usr/lib32/clang/19/include/opencl*': No such file or directory
Changing _major_ver to 20 in the PKGBUILD fixes it.
thank you, d3vilguard.
lib32-clang functionality is fully restored now.
Confirming build successful in a clean chroot!
Test builds in clean chroot have been succesfull, please comfirm if it works for you.
deleted
Thank you for your continued work on this. It is greatly appreciated.
Thanks archdevlab. Your result with building separately confirmed my thoughts why build on (some) live systems worked but failed in clean chroot.
I have found a promising workaround (extending LD_LIBRARY_PATH) and am now testing it. first testrun with mkchrootpkg (with custom makepkg.conf) has just finished successfully! .
As for building separate packages : I have tried that many times over the years and had to abandon it every time due to build & runtime issues. Longest period they worked was less then a month.
If you look at the PKGBUILDs for repo llvm & clang packages, you'll notice they list extra stuff in source= array, cmake-$pkgver.src.tar.xz & third-party-$pkgver.src.tar.xz .
I don't know what's in them or where they are generated from but the release builds do need them. Building in-tree doesn't require sources apart from the llvm-project repo.
Hi I was getting the issue with lib32-clang. The intree build fail. So I managed to build separate package. Now It build fine
You can take a look.
https://github.com/archdevlab/llvm-minimal-git/tree/test2/llvm-test
Hope It will help you
Also compiler-rt files goes in the right place like Archlinux when building it in separate pakcage (/usr/lib/clang/$Version/include /usr/lib/clang/$Version/lib/linux /usr/lib/clang/$Version/share) instead of (/usr/lib/clang/$Version/include /usr/lib/clang/$Version/lib/{i386-pc-linux-gnu,x86_64-pc-linux-gnu} /usr/lib/clang/$Version/share) when doing intree build
It appears that upstream has managed to solve the build issues for lib32-clang caused by commit 91a384621e5b762d9c173ffd247cfeadd5f436a2
I'll be testing the PKGBUILD below over the next few days to verify.
Incase someone wants to help, try building it in a clean chroot or VM.
removed, see above for improved version
Sorry Lone_Wolf, I mean, I need this to build this package to build lib32-mesa-git.
Is this able to be built now? If so what needs to be done to achieve this?
Pinned Comments
Lone_Wolf commented on 2024-02-20 11:59 (UTC)
https://github.com/llvm/llvm-project/commit/91a384621e5b762d9c173ffd247cfeadd5f436a2 changed soname and broke this package.
Lone_Wolf commented on 2019-08-21 13:47 (UTC)
When building this you're likely to get test failures.
The ones related to tools/gold are a consequence of certain choices and should be unimportant.
Use --nocheck option to prevent makepkg from running the check() function