This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libgcc/58120] New: libgcc.a and libgcc_eh.a have incorrect symbol visibility


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]