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.
# cat /etc/redhat-release
Red Hat Enterprise Linux release 8.9 Beta (Ootpa)
# rpm -q binutils gcc-toolset-13-binutils
package binutils is not installed
# dnf install -y gcc-toolset-13-binutils
[...]
# ld
-bash: /usr/bin/ld: No such file or directory
That's expected. But:
# dnf install -y binutils
[...]
the primary link for ld must be /opt/rh/gcc-toolset-13/root/usr/bin/ld
the primary link for ld must be /opt/rh/gcc-toolset-13/root/usr/bin/ld
# ld
-bash: /usr/bin/ld: No such file or directory
is not.
I think that this is happening because the gcc-toolset-13-binutils spec file is using the system version of the "alternatives" script, rather than the GTS-13 version. ie https://bugzilla.redhat.com/show_bug.cgi?id=2209148
But that should have been fixed by the gcc-toolset-13-binutils-2.40-8.el9 build, so I need to investigate further.
OK, so it is the alternatives system which is generating this message, but I am not sure exactly what it means or how to fix it.
Oh, and the "fixed" binutils build for BZ 2209148 is being used, so it may be that the fix for that BZ is actually wrong...
The problem exists if you perform the opposite installation sequence too:
# dnf install -y binutils
[...]
# dnf install -y gcc-toolset-13-binutils
[...]
the primary link for ld must be /usr/bin/ld
the primary link for ld must be /usr/bin/ld
[...]
# /opt/rh/gcc-toolset-13/root/usr/bin/ld
sh: /opt/rh/gcc-toolset-13/root/usr/bin/ld: No such file or directory
Still investigating.
Should be fixed by: gcc-toolset-13-binutils-2.40-11.el8
The problem - I think - is that the gcc-toolset-13-binutils needs to use the alternatives script with the --altdir and --admindir options set to point to the gts-13 equivalents. Then it will not interfere with the alternatives used by the system binutils.
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 (gcc-toolset-13-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/RHEA-2023:6983