public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/45258] linkage on -ldl, -lm and -lpthread should be purged from darwin build Date: Mon, 10 Jan 2011 20:25:00 -0000 [thread overview] Message-ID: <bug-45258-4-LvTUj7kZkx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-45258-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45258 Iain Sandoe <iains at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |iains at gcc dot gnu.org --- Comment #14 from Iain Sandoe <iains at gcc dot gnu.org> 2011-01-10 20:07:09 UTC --- if we could get Java and libquadmath to intercept the new LINK_GCC_C_SEQUENCE_SPEC instead of re-writing the *lib sequence it would give us a little more room to maneuver. .. as it is when another part of the complier hijacks the *lib sequence it happens too late for the target to intervene -- anything inserted as a '-l*' is untouchable at that stage. if we have the option to re-write from the start of LINK_GCC_C_SEQUENCE_SPEC we're in with a chance... otherwise .. the only solution then is to apply target-specific stuff in the lib/java builds.
next prev parent reply other threads:[~2011-01-10 20:07 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-45258-4@http.gcc.gnu.org/bugzilla/> 2011-01-10 19:08 ` rwild at gcc dot gnu.org 2011-01-10 19:59 ` howarth at nitro dot med.uc.edu 2011-01-10 20:07 ` mrs at gcc dot gnu.org 2011-01-10 20:25 ` iains at gcc dot gnu.org [this message] 2011-01-10 20:56 ` howarth at nitro dot med.uc.edu 2010-08-11 16:31 [Bug target/45258] New: linkage on " howarth at nitro dot med dot uc dot edu 2010-08-12 3:41 ` [Bug target/45258] linkage on -ldl, " howarth at nitro dot med dot uc dot edu 2010-08-12 3:42 ` howarth at nitro dot med dot uc dot edu 2010-08-12 4:01 ` howarth at nitro dot med dot uc dot edu 2010-08-12 4:03 ` howarth at nitro dot med dot uc dot edu 2010-08-12 4:12 ` howarth at nitro dot med dot uc dot edu 2010-08-12 5:52 ` howarth at nitro dot med dot uc dot edu 2010-08-12 11:23 ` howarth at nitro dot med dot uc dot edu
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-45258-4-LvTUj7kZkx@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: 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).