Summary: | dev-util/bcc-0.19.0 - Unable to find clang libraries | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Zac Medico <zmedico> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | chutzpah, holger |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge-info.txt
CMakeOutput.log dev-util:bcc-0.19.0:20210418-034311.log emerge-history.txt environment etc.portage.tar.bz2 logs.tar.bz2 temp.tar.bz2 |
Description
Toralf Förster
2021-04-18 08:48:06 UTC
Created attachment 700500 [details]
emerge-info.txt
Created attachment 700503 [details]
CMakeOutput.log
Created attachment 700506 [details]
dev-util:bcc-0.19.0:20210418-034311.log
Created attachment 700509 [details]
emerge-history.txt
Created attachment 700512 [details]
environment
Created attachment 700515 [details]
etc.portage.tar.bz2
Created attachment 700518 [details]
logs.tar.bz2
Created attachment 700521 [details]
temp.tar.bz2
bcc is one of the packages that simply don't build with clang-12 yet because libclangBasic and others were removed and aggregated into libclang-cpp (so that consumers only link against one lib, not many, and constantly break). See: https://fedoraproject.org/wiki/Changes/Stop-Shipping-Individual-Component-Libraries-In-clang-lib-Package (In reply to Holger Hoffstätte from comment #9) > bcc is one of the packages that simply don't build with clang-12 yet because > libclangBasic and others were removed and aggregated into libclang-cpp > (so that consumers only link against one lib, not many, and constantly > break). > See: > https://fedoraproject.org/wiki/Changes/Stop-Shipping-Individual-Component- > Libraries-In-clang-lib-Package Actually that already seems to be the case with bcc commit e46997e9a4 where they added fallbacks and try to find libclang-ccp, yay. It seems the real problem is in the ebuild because it allows <=sys-devel/clang-13:= but then sets LLVM_MAX_SLOT=11. This seems to confuse everyone involved esp. when both 11 and 12 are installed. Since I hacked my mesa ebuild to allow llvm:12 (works fine) and no longer have llvm/clang:11 installed, I bumped LLVM_MAX_SLOT to 12 and can now build all of libbpf/bcc/bpftrace without problems or further changes. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4ab1a18d0f7017ebb87017dc429eb154aac78c78 commit 4ab1a18d0f7017ebb87017dc429eb154aac78c78 Author: Jakov Smolić <jsmolic@gentoo.org> AuthorDate: 2021-11-07 20:58:09 +0000 Commit: Jakov Smolić <jsmolic@gentoo.org> CommitDate: 2021-11-07 20:58:36 +0000 dev-util/bcc: drop 0.19.0-r1, 0.20.0-r1 Newer versions have fixed issues with allowed llvm slots. gethostlatency seems to work fine with version 0.22.0-r1 Closes: https://bugs.gentoo.org/783693 Closes: https://bugs.gentoo.org/782736 Signed-off-by: Jakov Smolić <jsmolic@gentoo.org> dev-util/bcc/Manifest | 2 - dev-util/bcc/bcc-0.19.0-r1.ebuild | 107 -------------------------------------- dev-util/bcc/bcc-0.20.0-r1.ebuild | 107 -------------------------------------- 3 files changed, 216 deletions(-) |