public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/42033] libstdc++ seems to miss std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string<char*>(char*, char*, std::allocator<char> const&)
Date: Tue, 28 Apr 2015 09:24:00 -0000 [thread overview]
Message-ID: <bug-42033-4-wFul9a1ww1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-42033-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42033
--- Comment #13 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Manoj from comment #12)
> I am facing a similar issue. Following is the error that I am facing at run
> time:
This is not similar at all. This bug was about a failure to link, if you are
getting an error at run-time then you have successfully linked and it is not
the same issue.
Instead of commenting here please try emailing the gcc-help@gcc.gnu.org mailing
list, including a more complete description of your problem (you didn't say
what's wrong, just showed a stack trace).
next prev parent reply other threads:[~2015-04-28 9:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-42033-4@http.gcc.gnu.org/bugzilla/>
2010-09-29 13:31 ` manu at gcc dot gnu.org
2010-12-12 20:48 ` hubicka at gcc dot gnu.org
2015-04-28 5:23 ` mannu7410 at gmail dot com
2015-04-28 9:24 ` redi at gcc dot gnu.org [this message]
2009-11-13 19:25 [Bug c++/42033] New: " hubicka at gcc dot gnu dot org
2009-11-13 20:09 ` [Bug c++/42033] " jason at gcc dot gnu dot org
2009-11-13 20:37 ` paolo dot carlini at oracle dot com
2009-11-13 21:02 ` hubicka at ucw dot cz
2009-11-13 21:11 ` paolo dot carlini at oracle dot com
2009-11-13 21:16 ` hubicka at ucw dot cz
2009-11-13 21:59 ` rguenth at gcc dot gnu dot org
2009-11-13 21:59 ` rguenth at gcc dot gnu dot org
2009-11-13 23:18 ` jason at redhat dot com
2010-09-13 15:23 ` paolo dot carlini at oracle dot com
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-42033-4-wFul9a1ww1@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).