Bug 1403609

Summary: ld: -Wl,--version-script fails to match symbols
Product: Red Hat Enterprise Linux 7 Reporter: Jan Engelhardt <jengelh>
Component: binutilsAssignee: Nick Clifton <nickc>
Status: CLOSED CURRENTRELEASE QA Contact: qe-baseos-tools-bugs
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.4CC: law, mnewsome
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 13:48:59 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:
Bug Depends On:    
Bug Blocks: 1473718    

Description Jan Engelhardt 2016-12-11 21:22:39 UTC 
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
Comment 2 Nick Clifton 2016-12-13 12:53:20 UTC 
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
Comment 4 Jan Engelhardt 2017-08-07 22:37:37 UTC 
The issue is fixed with that update.