From: David Edelsohn <dje@watson.ibm.com>
To: Andreas Jaeger <aj@suse.de>
Cc: Mark Mitchell <mark@codesourcery.com>,
Nathan Sidwell <nathan@codesourcery.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: "*INTERNAL*" appended to function name bootstrap failure
Date: Wed, 05 Dec 2001 07:48:00 -0000 [thread overview]
Message-ID: <200112051547.KAA26392@makai.watson.ibm.com> (raw)
In-Reply-To: Message from Andreas Jaeger <aj@suse.de> of "Wed, 05 Dec 2001 14:35:30 +0100." <ho667l7pst.fsf@gee.suse.de>
I was able to bootstrap after updating again. I suspect that the
patch was modified in the tree.
David
next prev parent reply other threads:[~2001-12-05 15:48 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
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 [this message]
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=200112051547.KAA26392@makai.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=aj@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
--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).