public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Nathanael Nerode <neroden@twcny.rr.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/8953: ...
Date: Sat, 11 Jan 2003 20:26:00 -0000 [thread overview]
Message-ID: <20030111202601.16469.qmail@sources.redhat.com> (raw)
The following reply was made to PR libstdc++/8953; it has been noted by GNATS.
>From neroden@twcny.rr.com Mon Jan 13 00:59:33 2003
From: Nathanael Nerode <neroden@twcny.rr.com>
To: gcc-gnats@gcc.gnu.org, koffle@telia.com, Jonas.Jonsson@alcesys.se,
gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org
Cc:
Subject: Re: libstdc++/8953: ...
Date: Sat, 11 Jan 2003 15:21:18 -0500
Bug reporter: Can you 'make check' on your system with mainline CVS gcc and
see if you still get the unexpected failures?
A lot has changed since 3.2.1. I'm not seeing those errors, but I'm not
using a Solaris x86 system, of course.
reply other threads:[~2003-01-11 20:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030111202601.16469.qmail@sources.redhat.com \
--to=neroden@twcny.rr.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).