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.
DescriptionYaakov Selkowitz
2015-12-01 17:46:17 UTC
The version of gcc with which libtool has been built is hard-coded into /usr/bin/libtool, requiring the latter to be rebuilt every time gcc is version-bumped. In RHEL 7.2, gcc was bumped to 4.8.5 but libtool has yet to be rebuilt. This prevents packages which use /usr/bin/libtool from being (re)built (e.g. epel7 geos).
Please revbump and rebuild libtool for 7.2.z and 7.3.
For the purposes of QA, these lines are supposed to prevent this from being missed:
%global gcc_version 4.8.2
[snip]
# /usr/bin/libtool includes paths within gcc's versioned directories
# Libtool must be rebuilt whenever a new upstream gcc is built
Requires: gcc = %{gcc_version}
but for whatever reason, this doesn't seem to help.
(In reply to Yaakov Selkowitz from comment #0)
> Please revbump and rebuild libtool for 7.2.z and 7.3.
We should really fix this ASAP, thanks for the report (it should have been
done already -- together with gcc).
Reason for safety check not working can be seen here:
$ rpm -q --provides gcc
bundled(libiberty)
gcc = 4.8.2-16.el7
gcc = 4.8.5-4.el7
gcc(x86-64) = 4.8.5-4.el7
libgcc48privatecloog-isl.so.4()(64bit)
liblto_plugin.so.0()(64bit)
Somebody added Provides: which breaks this safety check.
I suggest using Conflicts: gcc_version + 1
For new build:
Conflicts: gcc >= 4.8.6
(In reply to Tuomo Soini from comment #10)
> Reason for safety check not working can be seen here:
Yes, obviously.
> I suggest using Conflicts: gcc_version + 1
>
> For new build:
>
> Conflicts: gcc >= 4.8.6
This sounds like good idea.
The process of relevant async errata is probably too far to have it fixed
right now. I would be OK with respin if QA was OK too.
Comment 12Yaakov Selkowitz
2015-12-28 21:50:23 UTC
(In reply to Tuomo Soini from comment #10)
> Reason for safety check not working can be seen here:
>
> $ rpm -q --provides gcc
> bundled(libiberty)
> gcc = 4.8.2-16.el7
> gcc = 4.8.5-4.el7
> gcc(x86-64) = 4.8.5-4.el7
> libgcc48privatecloog-isl.so.4()(64bit)
> liblto_plugin.so.0()(64bit)
>
> Somebody added Provides: which breaks this safety check.
Indeed, although I don't understand why:
%if 0%{?rhel} == 7
%global gcc_version 4.8.2
%else
%global gcc_version 4.8.5
%endif
Version: 4.8.5
Release: %{gcc_release}%{?dist}
%if "%{version}" != "%{gcc_version}"
%define gcc_provides %{gcc_version}-16%{?dist}
%endif
Comment 14Yaakov Selkowitz
2015-12-29 04:38:12 UTC
(In reply to Tuomo Soini from comment #13)
> Note: %rhel == 7.
Yes, I got *that* part. I don't understand why this being done in the first place though.
I can only guess but compatibility with old version is only reason I could guess.
Comment 16Yaakov Selkowitz
2016-11-04 19:44:11 UTC
RHEL 7.3 shipped with libtool-2.4.2-21.el7_2, which includes this fix. Can this be closed?
Comment 18RHEL Program Management
2020-12-15 07:38:54 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.