public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "htl10 at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/64390] "-shared" does not resolve symbols from lto generated archives Date: Wed, 24 Dec 2014 16:03:00 -0000 [thread overview] Message-ID: <bug-64390-4-kRlLnF693z@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64390-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64390 --- Comment #3 from Hin-Tak Leung <htl10 at users dot sourceforge.net> --- I wonder if it isn't '-shared' but that a mixture of object files and archives are being used. See also: http://stackoverflow.com/questions/27372667/undefined-reference-cross-compiling-static-libraries-with-lto-under-gcc I 'll give binutils 2.25 a try soon - I have got something building atm; it looks like I need to move my system's ar & ld aside to make sure the new ones are used, which is not trivial, and can't happen while I have something building anyway...
next prev parent reply other threads:[~2014-12-24 16:03 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-23 18:57 [Bug ipa/64390] New: " htl10 at users dot sourceforge.net 2014-12-23 18:59 ` [Bug ipa/64390] " htl10 at users dot sourceforge.net 2014-12-24 16:03 ` htl10 at users dot sourceforge.net [this message] 2014-12-24 21:45 ` htl10 at users dot sourceforge.net
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-64390-4-kRlLnF693z@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).