Bug 1947131 - clang module_el8 binary is broken if llvm-libs rc2.module_el8 rpm is installed
Summary: clang module_el8 binary is broken if llvm-libs rc2.module_el8 rpm is installed
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: clang
Version: CentOS Stream
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: beta
: ---
Assignee: Tom Stellard
QA Contact: Miloš Prchlík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-07 18:47 UTC by Edward Pilatowicz
Modified: 2021-09-17 08:40 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-02 02:03:08 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Edward 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<---

Comment 1 Tom Stellard 2021-04-30 22:44:09 UTC
Thank you for reporting.  We are going to look into some packaging changes to make sure this doesn't happen in the future.

Comment 2 Tom Stellard 2021-07-02 02:03:08 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.