Search Criteria
Package Details: clang-prefixed-release 18.1.3-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/clang-prefixed-release.git (read-only, click to copy) |
---|---|
Package Base: | clang-prefixed-release |
Description: | Up to date official clang releases installed at /opt/clang/latest to avoid system wide usage/impact |
Upstream URL: | https://llvm.org/ |
Licenses: | custom:Apache 2.0 with LLVM Exception |
Submitter: | sirspudd |
Maintainer: | sirspudd |
Last Packager: | sirspudd |
Votes: | 2 |
Popularity: | 0.005399 |
First Submitted: | 2023-01-26 02:02 (UTC) |
Last Updated: | 2024-04-04 17:53 (UTC) |
Dependencies (17)
- clang (llvm-rocm-gitAUR, llvm-gitAUR, clang-minimal-gitAUR) (make)
- cmake (cmake-gitAUR) (make)
- git (git-gitAUR) (make)
- jsoncpp (jsoncpp-cmake-gitAUR, jsoncpp-cmakeAUR, jsoncpp-gitAUR) (make)
- libc++ (libc++-msanAUR, libc++-modulesAUR) (make)
- libedit (make)
- libffi (libffi-gitAUR) (make)
- libxml2 (libxml2-gitAUR, libxml2-2.9AUR) (make)
- lld (llvm-rocm-gitAUR, llvm-gitAUR) (make)
- ncurses (ncurses-gitAUR) (make)
- ninja (ninja-kitwareAUR, ninja-memAUR, ninja-fuchsia-gitAUR, ninja-gitAUR) (make)
- ocl-icd (khronos-ocl-icd-gitAUR, khronos-ocl-icdAUR) (make)
- opencl-headers (opencl-headers-gitAUR) (make)
- python (python32AUR, python37AUR, python310AUR) (make)
- swig (swig-gitAUR) (make)
- z3 (z3-javaAUR, z3-gitAUR) (make)
- python-psutil (check)
Latest Comments
1 2 3 Next › Last »
sirspudd commented on 2024-01-30 21:49 (UTC)
Cool; I have verified 18.1 rc1 builds with gcc (without libc) and builds with clang 17 (it does not build with the clang in the Arch repos)
shardik commented on 2023-11-29 18:32 (UTC)
I ran in the same error, failing to build 17.0.5 with clang 16. Then I tried to build 17.0.1 with clang 16, wich works. So you can build 17.0.1 with system clang (16), and then, with 17.0.1 installed and added to $PATH, build 17.0.5.
sirspudd commented on 2023-11-22 20:05 (UTC)
@lahwaacz there is a convenient bool you can now toggle to have clang 17.0.5 break with with gcc (13) or the system clang (16). I would recommend the clang-github-bin package which bypasses this bootstrap problem. I nearly added it as a dependency to building this package, but this feels a little user hostile to do this behind the scenes.
sirspudd commented on 2023-11-22 19:06 (UTC)
Ok, I have confirmed that compiling with gcc explodes for its own reasons; I went through the easy fixes, but there is some legitimate unhappiness there which makes proceeding hard
sirspudd commented on 2023-11-22 18:21 (UTC)
@lahwaacz I saw this happen against clang 16 which is unfortunately what the mother ship is packing; it does not happen against clang 17. I could modify the recipe for clang to be built by gcc by default, but I prefer dogfooding. If you modify the recipe by removing the 2 lines which nominate clang as the compiler, I believe you should be golden. I will try to make the recipe easier to flip between gcc and clang host compilation, and will test building with gcc
lahwaacz commented on 2023-11-22 12:34 (UTC)
Building 17.0.5-1 in a clean chroot failed for me:
sirspudd commented on 2023-09-10 21:49 (UTC)
@lahwaacz: this plugin is not present in the official clang package either. I am now building it via explicit inclusion of the binutil include path, so it is present as of 17rc4-2
lahwaacz commented on 2023-09-09 16:43 (UTC)
It seems that the gold linker is gone?
sirspudd commented on 2023-05-11 15:58 (UTC)
@lahwaacz thanks for discovering the source of the issue, I updated the PKGBUILD to reflect this build req
lahwaacz commented on 2023-05-11 15:14 (UTC)
@sirspudd Looking a bit further, I noticed this warning during the configure step:
It seems that in the end, clang++ was using GCC's libstdc++ instead of the LLVM libc++, which lead to the errors. So I added
libc++
tomakedepends
and now the build seems to work...1 2 3 Next › Last »