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.
Hi Miloš,
If you have a look in one of the ld.log files for the common set of failures you will quickly discover the cause of most of the problems:
annobin: /root/rpmbuild/BUILD/binutils-2.32/ld/testsuite/ld-plugin/pr12758b.c: Warning: -D_FORTIFY_SOURCE not defined
And similarly for other source files. *sigh* I will investigate and see if there is a reason for omitting this command line option, or if it is just a problem with the test harness.
Cheers
Nick
Hi Miloš,
I now have a fix for the problem, but I do not think that it will be accepted for 8.2.0 as these now need blocker+ or exception+. Since the problem is only a bug in the linker testsuite harness and not the linker itself, I doubt that this BZ will qualify for either of those. Instead I have set the ITR field to 8.3.0 so that the fix can be applied with the next release.
Cheers
Nick
Understood, since it's just a test suite problem, I don't see any reason why to push this forward at this moment, 8.3 will be perfectly fine, in the meantime, I can update my test wrapper. Thanks!
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 (new packages: gcc-toolset-10-binutils), 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-2020:4780