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:
Static builds fail because the libquadmath.a 64bit libs are missing (only a broken symlink to a missing 32bit libquadmath.a gets installed
Version-Release number of selected component (if applicable):
gcc-8.3.1-4.5.el8.x86_64
How reproducible:
always
Steps to Reproduce:
1. install a development system for 64bit
2. observe broken symlinks to old 32bit libs
Actual results:
ls: cannot access '../../../i686-redhat-linux/8/libquadmath.a': No such file or directory
Expected results:
a 64bit libquadmath.a file in the appropriate place
Additional info:
[root@hpz SPECS]# locate quadmath.a
/usr/lib/gcc/x86_64-redhat-linux/8/32/libquadmath.a
[root@hpz SPECS]# rpm -q --whatprovides /usr/lib/gcc/x86_64-redhat-linux/8/32/libquadmath.a
gcc-8.3.1-4.5.el8.x86_64
[root@hpz SPECS]# dir /usr/lib/gcc/x86_64-redhat-linux/8/32/libquadmath.a
lrwxrwxrwx. 1 root root 42 Nov 6 2019 /usr/lib/gcc/x86_64-redhat-linux/8/32/libquadmath.a -> ../../../i686-redhat-linux/8/libquadmath.a
[root@hpz SPECS]# cd /usr/lib/gcc/x86_64-redhat-linux/8/32/
[root@hpz 32]# dir ../../../i686-redhat-linux/8/libquadmath.a
ls: cannot access '../../../i686-redhat-linux/8/libquadmath.a': No such file or directory
[root@hpz 32]#
This is expected; the static libraries (libquadmath-static in this case) are not shipped in RHEL 8 as we don't want to encourage or support static linking in RHEL 8. Sorry about that.
This makes no sense? Static linking is how reliable software can be shipped that keeps working despite you guys making under-the-hood changes, plus you're already shipping the 32bit equivalent for this, plus the 32 and 64 bit static libs for almost every other module - making your excuse highly inconsistent with reality.
Is that "we don't want to encourage or support static linking in RHEL 8." a real policy, or a made up excuse for why this bug is not going to get fixed? I get that 5 months looks bad for an open bug, but closing something that kills customer products instead of spending the 30mins on a fix seems like a decision that your managers are unlikely to endorse?
Red Hat discourages the use of static linking in applications for Red Hat Enterprise Linux. Therefore some of the -static libraries aren't shipped to customers.
We don't provide the 32-bit version of libquadmath, either; I've now fixed the dead symlinks.