public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Matthew Schalit <mschalit@pacbell.net> To: bkoz@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: libstdc++/2086 Date: Wed, 14 Mar 2001 22:26:00 -0000 [thread overview] Message-ID: <20010315062601.14497.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR libstdc++/2086; it has been noted by GNATS. From: Matthew Schalit <mschalit@pacbell.net> To: bkoz@gcc.gnu.org Cc: gcc-gnats@gcc.gnu.org Subject: Re: libstdc++/2086 Date: Wed, 14 Mar 2001 22:25:15 -0800 bkoz@gcc.gnu.org wrote: > > Synopsis: bootstrap error, libstdc++-v3/src/local.cc: op - > > Responsible-Changed-From-To: unassigned->bkoz > Responsible-Changed-By: bkoz > Responsible-Changed-When: Wed Mar 14 13:32:47 2001 > Responsible-Changed-Why: > Answered it. > State-Changed-From-To: open->feedback > State-Changed-By: bkoz > State-Changed-When: Wed Mar 14 13:32:47 2001 > State-Changed-Why: > Waiting for response. > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2086&database=gcc Thank you very much for looking into this. I'm sorry but I never received your suggestion until now. I have binutils 2.10.1 installed, so GNU-as is available. I've been trying since 2.95.2.1 to get my gmake bootstrap to work with GNU-as. I can't get it to work. I submitted a GNATS report on it: http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2034&database=gcc That report is still open. Do you have any suggestions? Was C the right department to direct that report to? Thanks, Matthew
next reply other threads:[~2001-03-14 22:26 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-03-14 22:26 Matthew Schalit [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-06-06 23:26 libstdc++/2086 neil 2001-04-01 0:00 libstdc++/2086 bkoz 2001-03-14 13:36 libstdc++/2086 bkoz
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=20010315062601.14497.qmail@sourceware.cygnus.com \ --to=mschalit@pacbell.net \ --cc=bkoz@gcc.gnu.org \ --cc=gcc-prs@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: linkBe 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).