Bug 2003903

Summary: Libraries provided by clang12-libs are (sometimes) not in the library path
Product: [Fedora] Fedora Reporter: Zbigniew Jędrzejewski-Szmek <zbyszek>
Component: clang12Assignee: Tom Stellard <tstellar>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 35CC: tbaeder, tstellar
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-30 07:29:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2003533    

Description Zbigniew Jędrzejewski-Szmek 2021-09-14 06:29:56 UTC
Description of problem:
bcc-tools uses clang12-libs, and the tools fail to start with a linkage error about libclang.so.12.

clang12-libs-12.0.1-3.fc35.x86_64 has libraries in /usr/lib64/llvm12/lib/, as does llvm12-libs-12.0.1-2.fc35.x86_64. But the latter has an /etc/ld.so.conf.d/llvm12-x86_64.conf which adds /usr/lib64/llvm12/lib/ to the library path. So on one machine I happen to have both packages installed, and the tools work without setting the path. On the other machine, I have only clang12-libs, and manual setting of the path is required.

Please duplicate the ld.so.conf.d file in both packages, so that the clang12-libs are always available.

Version-Release number of selected component (if applicable):
clang12-libs-12.0.1-3.fc35.x86_64

How reproducible:
Deterministic

Steps to Reproduce:
1. (Make sure llvm12-libs is *not* installed.)
2. /usr/share/bcc/tools/execsnoop

Actual results:
$ /usr/share/bcc/tools/execsnoop
Traceback (most recent call last):
  File "/usr/share/bcc/tools/execsnoop", line 21, in <module>
    from bcc import BPF
  File "/usr/lib/python3.10/site-packages/bcc/__init__.py", line 26, in <module>
    from .libbcc import lib, bcc_symbol, bcc_symbol_option, bcc_stacktrace_build_id, _SYM_CB_TYPE
  File "/usr/lib/python3.10/site-packages/bcc/libbcc.py", line 17, in <module>
    lib = ct.CDLL("libbcc.so.0", use_errno=True)
  File "/usr/lib64/python3.10/ctypes/__init__.py", line 374, in __init__
    self._handle = _dlopen(self._name, mode)
OSError: libclang-cpp.so.12: cannot open shared object file: No such file or directory

Comment 1 Tom Stellard 2021-09-14 15:26:07 UTC
Do you have llvm-libs-12.0.1 installed (i.e. an older version of the main llvm package) ?

Comment 2 Zbigniew Jędrzejewski-Szmek 2021-09-14 16:22:31 UTC
No, I only have llvm-libs-12.0.0-5.fc35.x86_64.

Comment 3 Tom Stellard 2021-09-17 20:54:59 UTC
Pull Request: https://src.fedoraproject.org/rpms/clang12/pull-request/1

Comment 4 Ben Cotton 2022-11-29 17:04:34 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.