public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/58476] In top-level configure --disable-static should change default for --with-boot-ldflags Date: Fri, 20 Sep 2013 17:42:00 -0000 [thread overview] Message-ID: <bug-58476-4-gN1xjWlwpe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58476-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58476 Ian Lance Taylor <ian at airs dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|bootstrap failure with Go |In top-level configure |enabled |--disable-static should | |change default for | |--with-boot-ldflags --- Comment #3 from Ian Lance Taylor <ian at airs dot com> --- The default value for --with-boot-ldflags is "-static-libstdc++ -static-libgcc" (set in the top level configure.ac file). When the g++ driver sees -static-libstdc++, it puts -Bstatic before -lstdc++ and puts -Bdynamic after it. So when you build with --disable-static, the effect is that go1 is linked against some other libstdc++ that it finds on the system, not the one that was just built. So it is not surprising that something went wrong. I would say that if someone configures with --disable-static, we need to change the default value of --with-boot-ldflags.
next prev parent reply other threads:[~2013-09-20 17:42 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-09-19 13:56 [Bug bootstrap/58476] New: bootstrap failure with Go enabled tromey at gcc dot gnu.org 2013-09-19 15:45 ` [Bug bootstrap/58476] " ian at airs dot com 2013-09-20 16:46 ` tromey at gcc dot gnu.org 2013-09-20 17:42 ` ian at airs dot com [this message] 2015-05-06 20:05 ` [Bug bootstrap/58476] In top-level configure --disable-static should change default for --with-boot-ldflags michael at talosis dot ca
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-58476-4-gN1xjWlwpe@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).