Bug 1937698

Summary:	gcc: Remove libstdc++ symbols which are not going to be part of the GCC 11 upstream release
Product:	[Fedora] Fedora	Reporter:	Florian Weimer <fweimer>
Component:	gcc	Assignee:	Jonathan Wakely <jwakely>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	34	CC:	aoliva, dmalcolm, fweimer, jakub, jwakely, law, mpolacek, msebor, nickc, sipoyare
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1937700 (view as bug list)		Environment:
Last Closed:	2022-06-08 06:24:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1926594, 1959307, 1959310, 1959312, 1959316, 1959319, 1959320, 1959323
Bug Blocks:	1937700

Description Florian Weimer 2021-03-11 11:17:36 UTC

The following symbols will be removed from libstdc++.so.6 before the GCC 11 upstream release:

_ZNSt9once_flag11_M_activateEv
_ZNSt9once_flag9_M_finishEb

We need to make this change in Fedora as well (in stages; first avoid creating symbol references from new builds, rebuild packages, and then remove the symbol for real).

Comment 1 Nicolas Chauvet (kwizart) 2021-04-02 16:28:06 UTC

What is the best way to detect the usage of theses symbols in any (non-fedora) package ? rpm2cpio + readelf ?
Eventually, having the range of the affected gcc compiler would help (or the first known good compiler) ?


Thanks in advance.

Comment 2 Jonathan Wakely 2021-04-03 14:46:42 UTC

(In reply to Nicolas Chauvet (kwizart) from comment #1)
> What is the best way to detect the usage of theses symbols in any
> (non-fedora) package ? rpm2cpio + readelf ?

Yes, that works.

> Eventually, having the range of the affected gcc compiler would help (or the
> first known good compiler) ?

The broken std::call_once was committed upstream Nov 3 2020. Rawhide switched to gcc-11.0.0 in late November, so all versions of gcc-11.0.0 will create references to the broken symbols. The fixed gcc that doesn't create references to those symbols (but still has them in libstdc++.so for now) is gcc-11.0.1-0.2.fc34 / gcc-11.0.1-0.2.fc35 (but the earlier build, gcc-11.0.1-0.1, is still bad).

Comment 3 Ben Cotton 2022-05-12 16:52:36 UTC

This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Ben Cotton 2022-06-08 06:24:17 UTC

Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.