public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Dr. Ernst Molitor" <molitor@uni-bonn.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/8155: GCC-3.2 doesn't compile on Linux-2.4.19 with glibc-2.3 (with patch to gcc-3.2 applied!)
Date: Mon, 07 Oct 2002 22:16:00 -0000	[thread overview]
Message-ID: <20021008051603.3011.qmail@sources.redhat.com> (raw)

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

From: "Dr. Ernst Molitor" <molitor@uni-bonn.de>
To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org
Cc: ernst.molitor@uni-bonn.de
Subject: Re: libstdc++/8155: GCC-3.2 doesn't compile on Linux-2.4.19 with
	glibc-2.3 (with patch to gcc-3.2 applied!)
Date: 08 Oct 2002 07:10:09 +0200

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8155
 
 Dear GCC gurus, 
 
 thank you very much for your extremely fast action - with current
 gcc-3_2-branch CVS sources, the problem described under #8155 has
 disappeared, and "make bootstrap" runs like a charm.
 
 Thank you very much.
 
 With kindest regards,
 
 Ernst
 
 On Sun, 2002-10-06 at 09:56, gcc-gnats@gcc.gnu.org wrote:
 > Thank you very much for your problem report.
 > It has the internal identification `libstdc++/8155'.
 > The individual assigned to look at your
 > report is: unassigned. 
 > 
 > >Category:       libstdc++
 > >Responsible:    unassigned
 > >Synopsis:       libstdc++ doesn't compile (GCC-3.2 with B. Haible's patch applied, glibc-2.3)
 > >Arrival-Date:   Sun Oct 06 00:56:00 PDT 2002
 > 
 
 


             reply	other threads:[~2002-10-08  5:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-07 22:16 Dr. Ernst Molitor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-06  0:56 ernst.molitor

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=20021008051603.3011.qmail@sources.redhat.com \
    --to=molitor@uni-bonn.de \
    --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).