public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mrs at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/41605] Static linking of libgcc/libgfortran/libstdc++ can cause inconsistent symbol resolution.
Date: Thu, 08 Oct 2009 16:44:00 -0000	[thread overview]
Message-ID: <20091008164436.22198.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41605-17110@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from mrs at gcc dot gnu dot org  2009-10-08 16:44 -------
Oh, if one wanted to, one could have libgcc_s forward the EH calls into
/usr/lib/libgcc_s.1.dylib by dlopening it and then doing dlsym on the symbols
and calling them.  This would `fix' the programs that linked against a gcc
libgcc_s file that uses EH when run on a system that has EH on the system. 
With that technology, I think all the mismatching here, just goes away.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41605


  parent reply	other threads:[~2009-10-08 16:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06 15:46 [Bug target/41605] New: " developer at sandoe-acoustics dot co dot uk
2009-10-06 15:57 ` [Bug target/41605] " developer at sandoe-acoustics dot co dot uk
2009-10-06 17:08 ` developer at sandoe-acoustics dot co dot uk
2009-10-08 16:36 ` mrs at gcc dot gnu dot org
2009-10-08 16:44 ` mrs at gcc dot gnu dot org [this message]
2009-10-14 11:20 ` developer at sandoe-acoustics dot co dot uk
2009-10-14 13:28 ` mrs at gcc dot gnu dot org
2009-12-22 22:12 ` janis at gcc dot gnu dot org
2009-12-31  1:35 ` davek at gcc dot gnu dot org
2009-12-31 11:40 ` howarth at nitro dot med dot uc dot edu
2009-12-31 17:07 ` developer at sandoe-acoustics dot co dot uk
2009-12-31 20:42 ` jakub at gcc dot gnu dot org
2010-01-02 22:51 ` kargl at gcc dot gnu dot org
2010-01-03 22:46 ` rguenth at gcc dot gnu dot org
2010-01-04 11:49 ` developer at sandoe-acoustics dot co dot uk
2010-01-22  9:39 ` developer at sandoe-acoustics dot co dot uk

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=20091008164436.22198.qmail@sourceware.org \
    --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).