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.
Description of problem:
binutils-devel RPM no longer ships libiberty.a:
[root@localhost SPECS]# rpm -q --provides binutils
binutils = 2.35.2-32.el9
binutils(x86-64) = 2.35.2-32.el9
bundled(libiberty)
libbfd-2.35.2-32.el9.so()(64bit)
libctf-nobfd.so.0()(64bit)
libctf-nobfd.so.0(LIBCTF_1.0)(64bit)
libctf.so.0()(64bit)
libctf.so.0(LIBCTF_1.0)(64bit)
libopcodes-2.35.2-32.el9.so()(64bit)
[root@localhost SPECS]#
[root@localhost SPECS]# rpm -ql binutils-devel
/usr/include/ansidecl.h
/usr/include/bfd.h
/usr/include/bfd_stdint.h
/usr/include/bfdlink.h
/usr/include/ctf-api.h
/usr/include/ctf.h
/usr/include/demangle.h
/usr/include/diagnostics.h
/usr/include/dis-asm.h
/usr/include/libiberty.h
/usr/include/plugin-api.h
/usr/include/symcat.h
/usr/lib64/libbfd.a
/usr/lib64/libbfd.so
/usr/lib64/libctf-nobfd.a
/usr/lib64/libctf-nobfd.la
/usr/lib64/libctf.a
/usr/lib64/libctf.la
/usr/lib64/libopcodes.a
/usr/lib64/libopcodes.so
[root@localhost SPECS]#
The file seems to be missing yet announced in Provides, and it seems to be related to recent cross-binutils works. binutils-2.35.2-26 does ship it, binutils-2.35.2-27.el9 does not.
According to specfile, libiberty.a is build and installed, but then it's removed, unlike some other files:
869 %else
870 # For cross-binutils we drop the documentation.
871 rm -rf %{buildroot}%{_infodir}
872 # We keep these as one can have native + cross binutils of different versions.
873 #rm -rf {buildroot}{_prefix}/share/locale
874 #rm -rf {buildroot}{_mandir}
875 rm -rf %{buildroot}%{_libdir}/libiberty.a
876 # Remove libtool files, which reference the .so libs
877 rm -f %{buildroot}%{_libdir}/*.la
878 %endif
I'm not sure whether this is on purpose, in any case it might affect builds of other packages, I for one ran into this dyninst build issue:
-- ElfUtils includes: /usr/include;/usr/include/elfutils;/usr/include/elfutils
-- ElfUtils library dirs: /usr/lib64;/usr/lib64/elfutils;/usr/lib64;/usr/lib64;/usr/lib64/elfutils
-- ElfUtils libraries: /usr/lib64/libelf.so.1;/usr/lib64/libdw.so.1;/usr/lib64/libdebuginfod.so.1
CMake Error at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
Could NOT find LibIberty (missing: LibIberty_LIBRARIES)
Call Stack (most recent call first):
/usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE)
cmake/Modules/FindLibIberty.cmake:64 (find_package_handle_standard_args)
cmake/LibIberty.cmake:44 (find_package)
CMakeLists.txt:40 (include)
Version-Release number of selected component (if applicable):
binutils-2.35.2-32.el9
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (binutils bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:2548
Description of problem: binutils-devel RPM no longer ships libiberty.a: [root@localhost SPECS]# rpm -q --provides binutils binutils = 2.35.2-32.el9 binutils(x86-64) = 2.35.2-32.el9 bundled(libiberty) libbfd-2.35.2-32.el9.so()(64bit) libctf-nobfd.so.0()(64bit) libctf-nobfd.so.0(LIBCTF_1.0)(64bit) libctf.so.0()(64bit) libctf.so.0(LIBCTF_1.0)(64bit) libopcodes-2.35.2-32.el9.so()(64bit) [root@localhost SPECS]# [root@localhost SPECS]# rpm -ql binutils-devel /usr/include/ansidecl.h /usr/include/bfd.h /usr/include/bfd_stdint.h /usr/include/bfdlink.h /usr/include/ctf-api.h /usr/include/ctf.h /usr/include/demangle.h /usr/include/diagnostics.h /usr/include/dis-asm.h /usr/include/libiberty.h /usr/include/plugin-api.h /usr/include/symcat.h /usr/lib64/libbfd.a /usr/lib64/libbfd.so /usr/lib64/libctf-nobfd.a /usr/lib64/libctf-nobfd.la /usr/lib64/libctf.a /usr/lib64/libctf.la /usr/lib64/libopcodes.a /usr/lib64/libopcodes.so [root@localhost SPECS]# The file seems to be missing yet announced in Provides, and it seems to be related to recent cross-binutils works. binutils-2.35.2-26 does ship it, binutils-2.35.2-27.el9 does not. According to specfile, libiberty.a is build and installed, but then it's removed, unlike some other files: 869 %else 870 # For cross-binutils we drop the documentation. 871 rm -rf %{buildroot}%{_infodir} 872 # We keep these as one can have native + cross binutils of different versions. 873 #rm -rf {buildroot}{_prefix}/share/locale 874 #rm -rf {buildroot}{_mandir} 875 rm -rf %{buildroot}%{_libdir}/libiberty.a 876 # Remove libtool files, which reference the .so libs 877 rm -f %{buildroot}%{_libdir}/*.la 878 %endif I'm not sure whether this is on purpose, in any case it might affect builds of other packages, I for one ran into this dyninst build issue: -- ElfUtils includes: /usr/include;/usr/include/elfutils;/usr/include/elfutils -- ElfUtils library dirs: /usr/lib64;/usr/lib64/elfutils;/usr/lib64;/usr/lib64;/usr/lib64/elfutils -- ElfUtils libraries: /usr/lib64/libelf.so.1;/usr/lib64/libdw.so.1;/usr/lib64/libdebuginfod.so.1 CMake Error at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:230 (message): Could NOT find LibIberty (missing: LibIberty_LIBRARIES) Call Stack (most recent call first): /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE) cmake/Modules/FindLibIberty.cmake:64 (find_package_handle_standard_args) cmake/LibIberty.cmake:44 (find_package) CMakeLists.txt:40 (include) Version-Release number of selected component (if applicable): binutils-2.35.2-32.el9 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: