public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: David Edelsohn <dje@watson.ibm.com>
Cc: Nathan Sidwell <nathan@codesourcery.com>,
	"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: "*INTERNAL*" appended to function name bootstrap failure
Date: Tue, 04 Dec 2001 14:03:00 -0000	[thread overview]
Message-ID: <43440000.1007503149@warlock.codesourcery.com> (raw)
In-Reply-To: <200112042057.PAA23308@makai.watson.ibm.com>



--On Tuesday, December 04, 2001 03:57:01 PM -0500 David Edelsohn 
<dje@watson.ibm.com> wrote:

>>>>>> Mark Mitchell writes:
>
> Mark> Find the change that started causing this, and then we can fix it.
>
> 	This appears to be another secondary build error.  None of the
> changes in gcc/cp nor in libstdc++-v3/libsupc++ seem to have caused the
> problem.  I will try a few changes in gcc, but it seems less likely to
> have caused this problem.

That's pretty strange.  This could be a change to debugging generation
as well, I suppose.

-- 
Mark Mitchell                mark@codesourcery.com
CodeSourcery, LLC            http://www.codesourcery.com

  reply	other threads:[~2001-12-04 22:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-04 11:34 David Edelsohn
2001-12-04 11:36 ` Mark Mitchell
2001-12-04 12:57   ` David Edelsohn
2001-12-04 14:03     ` Mark Mitchell [this message]
2001-12-04 14:07       ` David Edelsohn
2001-12-04 14:11         ` Jakub Jelinek
2001-12-04 14:17           ` David Edelsohn
2001-12-05  5:35   ` Andreas Jaeger
2001-12-05  7:48     ` David Edelsohn
2001-12-05  8:27       ` Andreas Jaeger
2001-12-06  9:45         ` Alexandre Oliva

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=43440000.1007503149@warlock.codesourcery.com \
    --to=mark@codesourcery.com \
    --cc=dje@watson.ibm.com \
    --cc=gcc@gcc.gnu.org \
    --cc=nathan@codesourcery.com \
    /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).