Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionEdward Pilatowicz
2021-04-07 18:47:48 UTC
Description of problem:
After a recent update to the clang rpm, the clang binary started failing:
---8<---
# rpm -q clang
clang-11.0.0-1.module_el8.4.0+587+5187cac0.x86_64
# clang --version
clang: symbol lookup error: /lib64/libclang-cpp.so.11: undefined symbol: _ZN4llvm15OpenMPIRBuilder16getOrCreateIdentEPNS_8ConstantENS_3omp9IdentFlagEj, version LLVM_11
---8<---
When the same clang rpm is installed on a new host, the clang binary works fine. The failure seems to be caused by an outdated llvm-libs rpm. It seems that the clang rpm only specifies a dependency on LLVM_11:
---8<---
# dnf repoquery --requires clang-11.0.0-1.module_el8.4.0+587+5187cac0 | grep -i llvm
Last metadata expiration check: 0:23:37 ago on Wed 07 Apr 2021 09:43:57 AM PDT.
libLLVM-11.so()(64bit)
libLLVM-11.so(LLVM_11)(64bit)
---8<---
And on the failing host we have an older version of llvm-libs:
---8<---
# rpm -q llvm-libs
llvm-libs-11.0.0-0.6.rc2.module_el8.4.0+533+50191577.x86_64
---8<---
Where as on a freshly installed host we get the latest version of llvm-libs:
---8<---
# rpm -q llvm-libs
llvm-libs-11.0.0-2.module_el8.4.0+587+5187cac0.x86_64
---8<---
Updating clang does not force an update of llvm-libs
---8<---
# dnf update clang
Last metadata expiration check: 0:09:34 ago on Wed 07 Apr 2021 11:35:30 AM PDT.
Dependencies resolved.
Nothing to do.
Complete!
# rpm -q llvm-libs
llvm-libs-11.0.0-0.6.rc2.module_el8.4.0+533+50191577.x86_64
---8<---
Version-Release number of selected component (if applicable):
clang-11.0.0-1.module_el8.4.0+587+5187cac0.x86_64
llvm-libs-11.0.0-0.6.rc2.module_el8.4.0+533+50191577.x86_64
llvm-libs-11.0.0-2.module_el8.4.0+587+5187cac0.x86_64
How reproducible:
100%
Steps to Reproduce:
1. dnf install clang-11.0.0-1.module_el8.4.0+587+5187cac0.x86_64 llvm-libs-11.0.0-0.6.rc2.module_el8.4.0+533+50191577.x86_64
2. clang --version
3. profit
Actual results:
---8<---
# clang --version
clang: symbol lookup error: /lib64/libclang-cpp.so.11: undefined symbol: _ZN4llvm15OpenMPIRBuilder16getOrCreateIdentEPNS_8ConstantENS_3omp9IdentFlagEj, version LLVM_11
---8<---
Expected results:
---8<---
# clang --version
clang version 11.0.0 (Red Hat 11.0.0-1.module_el8.4.0+587+5187cac0)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /bin
---8<---
We are going to work with upstream to get SONAME bumps whenever the ABI changes in release candidates, but until then we are going to stop packging release candidates in CentOS Stream to avoid running into this problem.