public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at redhat dot com" <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: Fri, 13 Nov 2009 23:18:00 -0000 [thread overview]
Message-ID: <20091113231802.21194.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42033-176@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from jason at redhat dot com 2009-11-13 23:18 -------
Subject: Re: libstdc++ seems to miss std::basic_string<char,
std::char_traits<char>, std::allocator<char> >::basic_string<char*>(char*,
char*, std::allocator<char> const&)
On 11/13/2009 04:16 PM, hubicka at ucw dot cz wrote:
> I am confused why I get link error given that even my *.a exports the
> symbol...
Yeah, sounds more like a linker issue.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42033
next prev parent reply other threads:[~2009-11-13 23:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2010-09-13 15:23 ` paolo dot carlini at oracle dot com
[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
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=20091113231802.21194.qmail@sourceware.org \
--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).