[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug gold/21074] [2.28 Regression] bfd ld stumbles over duplicated symbo

From: nickc at redhat dot com
Subject: [Bug gold/21074] [2.28 Regression] bfd ld stumbles over duplicated symbols generated by gold
Date: Tue, 24 Jan 2017 10:04:34 +0000


--- Comment #6 from Nick Clifton <nickc at redhat dot com> ---
Hi Cary,

(In reply to Cary Coutant from comment #5)
> Something is missing from this test case, I think. It links fine with gold,
> and no duplicate symbols are generated.

That's strange - the test case works for me.  (Note- you need to use the bfd
linker to link the test case not gold).

> In the problem description, your
> __bss_start symbols have a Qt_5 version on them, but when I link your test
> case, I don't see any versions on those symbols.


  $ readelf --syms libapt-pkg.so.5.0  | grep bss_start
  963: 00000000003b14a0     0 NOTYPE  GLOBAL DEFAULT 25 __bss_start@@APTPKG_5.0

I do not know how GOLD resolves these symbol version conflicts.  Maybe it
converts them into absolute symbols first ?

> Apparently, ld is fine with duplicate absolute symbols, but it's not fine 
> with duplicate relative symbols. Seems to me you should fix ld so it does 
> diagnose the duplicate symbols in the absolute case. It should at least be 
> consistent.

Actually it is fine with duplicate absolute symbols that *have the same value*.
Which makes sense really.  Such symbols are just copies of each other. 
Redundant perhaps, but not really a cause for failing to link. 


You are receiving this mail because:
You are on the CC list for the bug.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]