public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "howarth at nitro dot med dot uc dot edu" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug boehm-gc/18135] gctest (boehm-gc) uses the installed libgcc_s on darwin Date: Fri, 19 Mar 2010 00:47:00 -0000 [thread overview] Message-ID: <20100319004732.27337.qmail@sourceware.org> (raw) In-Reply-To: <bug-18135-6528@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from howarth at nitro dot med dot uc dot edu 2010-03-19 00:47 ------- Andrew, Do you still see this issue with current gcc trunk since... Author: andreast Date: Wed Nov 18 07:36:12 2009 New Revision: 154282 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=154282 Log: 2009-11-18 Iain Sandoe <iain.sandoe@sandoe-acoustics.co.uk> PR other/39888 * config/t-slibgcc-darwin: Fix embedded rpaths for --enable-version-specific-runtime-libs, build extension stub libs exposing features available from current libgcc_s. Modified: trunk/libgcc/ChangeLog trunk/libgcc/config/t-slibgcc-darwin Author: andreast Date: Wed Nov 18 07:37:04 2009 New Revision: 154283 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=154283 Log: 2009-11-18 Iain Sandoe <iain.sandoe@sandoe-acoustics.co.uk> PR other/39888 * config/darwin.h: Use the extension stub libraries to access current libgcc_s features. Modified: trunk/gcc/ChangeLog trunk/gcc/config/darwin.h We should be linked to both the system libgcc_s and the FSF libgcc_s now (although filtered by the appropriate stubs for libgcc and libgcc_ext. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18135
next parent reply other threads:[~2010-03-19 0:47 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-18135-6528@http.gcc.gnu.org/bugzilla/> 2010-03-19 0:47 ` howarth at nitro dot med dot uc dot edu [this message] [not found] <bug-18135-8172@http.gcc.gnu.org/bugzilla/> 2013-12-19 11:59 ` dominiq at lps dot ens.fr 2014-11-15 12:51 ` fxcoudert at gcc dot gnu.org
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=20100319004732.27337.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@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).