public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cary.lewis at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/17995] gcc-3.4.2/libstdc++-v3/libsupc++/eh_alloc.cc:34 Date: Sat, 02 May 2015 17:00:00 -0000 [thread overview] Message-ID: <bug-17995-4-Vod7x9XK1e@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-17995-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=17995 --- Comment #14 from Cary Lewis <cary.lewis at gmail dot com> --- It's this exact error. The 3rd stage fails. With the conflict about ::strstr and std::strstr
next prev parent reply other threads:[~2015-05-02 17:00 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-17995-4@http.gcc.gnu.org/bugzilla/> 2015-05-02 13:35 ` cary.lewis at gmail dot com 2015-05-02 16:25 ` redi at gcc dot gnu.org 2015-05-02 17:00 ` cary.lewis at gmail dot com [this message] 2015-05-02 17:13 ` redi at gcc dot gnu.org 2015-05-02 19:19 ` cary.lewis at gmail dot com 2015-05-02 22:51 ` redi at gcc dot gnu.org 2015-05-04 17:31 ` cary.lewis at gmail dot com 2015-05-04 20:59 ` redi at gcc dot gnu.org 2015-05-04 21:12 ` cary.lewis at gmail dot com [not found] <bug-17995-9467@http.gcc.gnu.org/bugzilla/> 2008-02-12 9:29 ` manu at gcc dot gnu dot org 2008-06-21 11:51 ` paolo dot carlini at oracle dot com 2004-10-14 8:57 [Bug libstdc++/17995] New: gcc-3.4.2/libstdc++-v3/libsupc++/eh_alloc.cc:34 realsong at hotmail dot com 2004-10-14 9:15 ` [Bug libstdc++/17995] gcc-3.4.2/libstdc++-v3/libsupc++/eh_alloc.cc:34 realsong at hotmail dot com 2004-10-14 9:18 ` realsong at hotmail dot com 2004-10-14 9:21 ` realsong at hotmail dot com 2004-10-14 13:22 ` pinskia at gcc dot gnu dot org 2004-10-15 1:23 ` realsong at hotmail dot com 2004-11-03 1:05 ` Jim_Brownfield at radical dot com 2004-11-03 1:07 ` Jim_Brownfield at radical dot com 2004-12-17 18:07 ` pmcnary at cameron dot net 2005-04-14 0:02 ` pinskia at gcc dot gnu dot 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=bug-17995-4-Vod7x9XK1e@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).