public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: David Dudley <david.dudley@starblade.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/8303: libstdc++-v3 library fails to compile, with "internal compiler error"
Date: Tue, 26 Nov 2002 10:02:00 -0000	[thread overview]
Message-ID: <20021119165632.1762.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/8303; it has been noted by GNATS.

From: David Dudley <david.dudley@starblade.com>
To: bangerth@dealii.org, david.dudley@starblade.com,
  gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
  gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/8303: libstdc++-v3 library fails to compile, with "internal compiler error"
Date: Tue, 19 Nov 2002 10:56:14 -0600

 On Friday 15 November 2002 06:52 pm, you wrote:
 > Synopsis: libstdc++-v3 library fails to compile, with "internal compiler
 > error"
 >
 > State-Changed-From-To: open->feedback
 > State-Changed-By: bangerth
 > State-Changed-When: Fri Nov 15 16:52:26 2002
 > State-Changed-Why:
 >     Does this still happen? I'm tempted to reclassify this as
 >     "bootstrap", rather than "c++" judging from the way you
 >     describe the failure.
 >
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&
 >pr=8303
 
 I'm tempted to say that it does, but havn't rebuilt the compiler in a while.  
 Will attempt same build, and report results.
 


             reply	other threads:[~2002-11-19 16:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-26 10:02 David Dudley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-21 18:16 bangerth
2002-10-21 10:56 david.dudley

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=20021119165632.1762.qmail@sources.redhat.com \
    --to=david.dudley@starblade.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).