public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jeremyhu at macports dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/58120] New: libgcc.a and libgcc_eh.a have incorrect symbol visibility
Date: Sat, 10 Aug 2013 16:14:00 -0000	[thread overview]
Message-ID: <bug-58120-4@http.gcc.gnu.org/bugzilla/> (raw)

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.


                 reply	other threads:[~2013-08-10 16:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-58120-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).