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:
RHEL7 ships with g++ 4.8.x, which is able to compile this C++11 snippet:
# rh.cpp
struct K { void f(void) const &; };
void K::f(void) const & {}
When this K::f function happens to be in a shared library and a -Wl,--version-script file is used,
# rh.sym
XYZ { global: extern "C++" { K::*; }; local: *; };
then K::f becomes hidden on RHEL7, because Someone At RedHat™ forgot to update binutils when they updated gcc. (Since binutils bundles libiberty that originates from gcc.)
Version-Release number of selected component (if applicable):
binutils-2.23.52.0.1
How reproducible:
$ g++ rh.cpp -std=gnu++11 -fPIC -shared -Wl,--version-script=rh.sym -o rh.so
$ nm rh.so | grep _Z
Actual results:
- 0000000000000618 t _ZNKR1K1fEv
- Unhappy user
- Programs trying to use rh.so fail at link stage:
rh.so: undefined reference to `_ZNKR1K1fEv'
Expected results:
- 0000000000000618 T _ZNKR1K1fEv
- Content user
Hi Jan,
> Version-Release number of selected component (if applicable):
> binutils-2.23.52.0.1
RHEL 7.3 is now using binutils 2.25.1 and it does not exhibit the problem
reported here. Is this a sufficient solution for you ?
Cheers
Nick
Description of problem: RHEL7 ships with g++ 4.8.x, which is able to compile this C++11 snippet: # rh.cpp struct K { void f(void) const &; }; void K::f(void) const & {} When this K::f function happens to be in a shared library and a -Wl,--version-script file is used, # rh.sym XYZ { global: extern "C++" { K::*; }; local: *; }; then K::f becomes hidden on RHEL7, because Someone At RedHat™ forgot to update binutils when they updated gcc. (Since binutils bundles libiberty that originates from gcc.) Version-Release number of selected component (if applicable): binutils-2.23.52.0.1 How reproducible: $ g++ rh.cpp -std=gnu++11 -fPIC -shared -Wl,--version-script=rh.sym -o rh.so $ nm rh.so | grep _Z Actual results: - 0000000000000618 t _ZNKR1K1fEv - Unhappy user - Programs trying to use rh.so fail at link stage: rh.so: undefined reference to `_ZNKR1K1fEv' Expected results: - 0000000000000618 T _ZNKR1K1fEv - Content user