public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: gdr@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/9580: basic_filebuf<> with custom traits_type fails to link
Date: Thu, 13 Feb 2003 20:56:00 -0000 [thread overview]
Message-ID: <20030213205600.29912.qmail@sources.redhat.com> (raw)
The following reply was made to PR libstdc++/9580; it has been noted by GNATS.
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: paolo@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org, peturr02@ru.is, gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/9580: basic_filebuf<> with custom traits_type fails to link
Date: 13 Feb 2003 21:54:39 +0100
paolo@gcc.gnu.org writes:
| Synopsis: basic_filebuf<> with custom traits_type fails to link
|
| Responsible-Changed-From-To: unassigned->gdr
| Responsible-Changed-By: paolo
| Responsible-Changed-When: Thu Feb 13 20:11:34 2003
| Responsible-Changed-Why:
| traits guru
| State-Changed-From-To: open->analyzed
| State-Changed-By: paolo
| State-Changed-When: Thu Feb 13 20:11:34 2003
| State-Changed-Why:
| Hi Gaby, could you please have a look at this one?
| It bears some similarities with libstdc++/8836, which you
| triaged as not a bug. Thanks!
I'm tempted to see this as a bug in our library...
Can someone recall me briefly why we can't make this work?
-- Gaby
next reply other threads:[~2003-02-13 20:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 20:56 Gabriel Dos Reis [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-17 20:10 paolo
2003-02-13 21:46 Paolo Carlini
2003-02-13 21:36 Gabriel Dos Reis
2003-02-13 21:26 Paolo Carlini
2003-02-13 21:21 paolo
2003-02-13 21:16 Gabriel Dos Reis
2003-02-13 21:06 Paolo Carlini
2003-02-13 20:11 paolo
2003-02-05 10:36 peturr02
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=20030213205600.29912.qmail@sources.redhat.com \
--to=gdr@integrable-solutions.net \
--cc=gcc-prs@gcc.gnu.org \
--cc=gdr@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).