public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/35401] [4.3/4.4 Regression] libstdc++ linked to system /usr/lib/libgcc_s.1.dylib not new gcc4.3 libgcc_s.1.dylib Date: Sun, 02 Mar 2008 17:53:00 -0000 [thread overview] Message-ID: <20080302175226.23472.qmail@sourceware.org> (raw) In-Reply-To: <bug-35401-15848@http.gcc.gnu.org/bugzilla/> ------- Comment #24 from jakub at gcc dot gnu dot org 2008-03-02 17:52 ------- If r131198 makes a difference, then I'm just guessing that while libgcc's install target depends on install-darwin-libgcc-stubs, install-leaf does not. So perhaps libgcc/config/t-slibgcc-darwin should change: ifeq ($(enable_shared),yes) all: $(INSTALL_FILES) -install: install-darwin-libgcc-stubs +install-leaf: install-darwin-libgcc-stubs endif to make sure the other *.dylib files are installed into gcc/ subdir too. BTW, there is really no problem on the ELF side, you are just wasting time trying to prove this bug affects anything but darwin. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35401
next prev parent reply other threads:[~2008-03-02 17:53 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 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 [this message] 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=20080302175226.23472.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: linkBe 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).