public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mmitchel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/27984] [4.2 Regression] installed libstdc++ testing broken
Date: Sat, 17 Jun 2006 00:26:00 -0000 [thread overview]
Message-ID: <20060617002338.1164.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27984-230@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from mmitchel at gcc dot gnu dot org 2006-06-17 00:23 -------
I consider this a key validation requirement. It should be possible to test
the toolchain after installation to validate the bits that will actually go out
to users. This does not work for all parts of the toolchain, but it has worked
for GCC, G++, and libstdc++ for some time, so this should be fixed.
--
mmitchel at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27984
next prev parent reply other threads:[~2006-06-17 0:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-10 13:22 [Bug libstdc++/27984] New: " jsm28 at gcc dot gnu dot org
2006-06-10 14:10 ` [Bug libstdc++/27984] " pinskia at gcc dot gnu dot org
2006-06-17 0:26 ` mmitchel at gcc dot gnu dot org [this message]
2006-06-17 9:24 ` pcarlini at suse dot de
2006-06-23 23:49 ` bkoz at gcc dot gnu dot org
2006-06-24 1:43 ` bkoz at gcc dot gnu dot org
2006-06-24 2:53 ` 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=20060617002338.1164.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).