This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libgcc/58120] New: libgcc.a and libgcc_eh.a have incorrect symbol visibility
- From: "jeremyhu at macports dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 10 Aug 2013 16:14:21 +0000
- Subject: [Bug libgcc/58120] New: libgcc.a and libgcc_eh.a have incorrect symbol visibility
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58120
Bug ID: 58120
Summary: libgcc.a and libgcc_eh.a have incorrect symbol
visibility
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libgcc
Assignee: unassigned at gcc dot gnu.org
Reporter: jeremyhu at macports dot org
If one builds a dylib using static libgcc.a, the libgcc symbols will be
exported by that library. One can mitigate this using an
-unexported_symbols_list, but that is sub-optimal. The static archives should
have the expected visibility to prevent re-export when built into a dylib.
This is an issue on OS X, and I assume the same issue exists on other platforms
as well.