public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "agn at noc dot soton dot ac dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/35401] libstdc++ linked to system /usr/lib/libgcc_s.1.dylib not new gcc4.3 libgcc_s.1.dylib
Date: Fri, 29 Feb 2008 22:31:00 -0000 [thread overview]
Message-ID: <20080229223056.21950.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35401-15848@http.gcc.gnu.org/bugzilla/>
------- Comment #16 from agn at noc dot soton dot ac dot uk 2008-02-29 22:30 -------
Many thanks to Jack Howarth for putting in this work to sort out the bug.
Given the comments on the gcc list, I'll reduce the severity of the bug from
blocker to critical.
What originally brought this bug to my notice was that a python extension
linked to gcc43/libstdc++.6.dylib and gcc43/libgcc_s.1.dylib gave a
segmentation fault when called.
I suspected that the use of conflicting c libraries gcc43/libgcc_s.1.dylib and
(implicitly, through gcc43/libstdc++.6.dylib) /usr/lib/libgcc_s.1.dylib might
be causing the segmentation fault.
On the other hand... a similar extension linked to gcc43/libgfortran.3.dylib
and gcc43/libgcc_s.1.dylib was ok, even though gcc43/libgfortran.3.dylib is
itself linked to /usr/lib/libgcc_s.1.dylib
Perhaps the mislinking has more effect on the libstdc++ than on libgfortran?
Apologies if (as is likely) my contribution here is based on ignorance.
George Nurser.
--
agn at noc dot soton dot ac dot uk changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|blocker |critical
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35401
next prev parent reply other threads:[~2008-02-29 22:31 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 20:52 [Bug c++/35401] New: " agn at noc dot soton dot ac dot uk
2008-02-29 2:53 ` [Bug c++/35401] " howarth at nitro dot med dot uc dot edu
2008-02-29 12:35 ` rwild at gcc dot gnu dot org
2008-02-29 14:01 ` howarth at nitro dot med dot uc dot edu
2008-02-29 14:04 ` howarth at nitro dot med dot uc dot edu
2008-02-29 14:58 ` jakub at gcc dot gnu dot org
2008-02-29 15:00 ` agn at noc dot soton dot ac dot uk
2008-02-29 15:51 ` howarth at nitro dot med dot uc dot edu
2008-02-29 16:04 ` howarth at nitro dot med dot uc dot edu
2008-02-29 16:06 ` rguenth at gcc dot gnu dot org
2008-02-29 16:13 ` howarth at nitro dot med dot uc dot edu
2008-02-29 16:53 ` howarth at nitro dot med dot uc dot edu
2008-02-29 20:16 ` howarth at nitro dot med dot uc dot edu
2008-02-29 20:17 ` howarth at nitro dot med dot uc dot edu
2008-02-29 20:18 ` howarth at nitro dot med dot uc dot edu
2008-02-29 20:30 ` howarth at nitro dot med dot uc dot edu
2008-02-29 20:32 ` howarth at nitro dot med dot uc dot edu
2008-02-29 22:31 ` agn at noc dot soton dot ac dot uk [this message]
2008-02-29 22:52 ` [Bug c++/35401] [4.3/4.4 Regression] " rguenth at gcc dot gnu dot org
2008-03-01 17:27 ` howarth at nitro dot med dot uc dot edu
2008-03-01 17:34 ` howarth at nitro dot med dot uc dot edu
2008-03-01 19:44 ` howarth at nitro dot med dot uc dot edu
2008-03-01 19:59 ` howarth at nitro dot med dot uc dot edu
2008-03-01 20:44 ` howarth at nitro dot med dot uc dot edu
2008-03-01 22:51 ` howarth at nitro dot med dot uc dot edu
2008-03-02 17:53 ` jakub at gcc dot gnu dot org
2008-03-02 19:33 ` howarth at nitro dot med dot uc dot edu
2008-03-02 19:34 ` howarth at nitro dot med dot uc dot edu
2008-03-02 22:08 ` [Bug target/35401] " jakub at gcc dot gnu dot org
2008-03-02 22:09 ` jakub at gcc dot gnu dot org
2008-03-02 22:18 ` andreast at gcc dot gnu dot org
2008-03-02 23:10 ` fang at csl dot cornell dot edu
2008-03-03 9:21 ` rsandifo at nildram dot co dot uk
2008-03-03 11:34 ` agn at noc dot soton dot ac 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=20080229223056.21950.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).