public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "michael at talosis dot ca" <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: Wed, 06 May 2015 20:05:00 -0000 [thread overview]
Message-ID: <bug-58476-4-gf13Eew9RO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58476-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58476
Michael Deutschmann <michael at talosis dot ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |michael at talosis dot ca
--- Comment #4 from Michael Deutschmann <michael at talosis dot ca> ---
I'm experiencing a problem almost exactly like this in the new GCC 5.1.0 --
link failures due to missing overloaded "istream::ignore" functions that go
away when --disable-static is removed from the configure line. However, it is
cc1 that is failing instead of go1 (which I'm not building).
> 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.
That appears not to be the problem, in my case at least. I've compared working
and non-working build trees, and the non-working one has a libstdc++.a file
that is missing several modules compared to the working one. One of them is
compatibility.o, which contains the missing functions.
prev parent reply other threads:[~2015-05-06 20:05 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 ` [Bug bootstrap/58476] In top-level configure --disable-static should change default for --with-boot-ldflags ian at airs dot com
2015-05-06 20:05 ` michael at talosis dot ca [this message]
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-gf13Eew9RO@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: link
Be 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).