public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Wolfram Gloger <Wolfram.Gloger@dent.med.uni-muenchen.de>
To: bernds@redhat.com
Cc: gcc@gcc.gnu.org
Subject: Re: making a 2.95.4 release
Date: Wed, 03 Apr 2002 02:57:00 -0000	[thread overview]
Message-ID: <200204031037.MAA43176@max.zk-i.med.uni-muenchen.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0203281805400.20135-100000@host140.cambridge.redhat.com> (message from Bernd Schmidt on Thu, 28 Mar 2002 18:10:24 +0000 (GMT))

Hello,

> It would be nice if the problems the 2.95 branch has with compiling glibc
> could be fixed - that might motivate me to have another go at a release.

What problems exactly are you referring to?  FWIW, I have successfully
compiled glibc-2.2.5 and glibc-2.2.90 from CVS (a couple of weeks ago)
with gcc-2.95-2.95.4.ds2-0.010604 (the Debian release from last June).
The former is my production glibc package and I see no problems.

So I suspect that whatever problems you mean, have been _long_ fixed,
at least in the Debian patch set.

Regards,
Wolfram.

  parent reply	other threads:[~2002-04-03 10:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-28  9:35 David O'Brien
2002-03-28  9:39 ` law
2002-03-28  9:58 ` Gerald Pfeifer
2002-04-02  1:09   ` Gerald Pfeifer
2002-04-02 10:51     ` Joe Buck
2002-03-28 10:19 ` Bernd Schmidt
2002-03-28 11:38   ` David O'Brien
2002-03-28 11:46     ` Philip Blundell
2002-03-28 12:10       ` David O'Brien
2002-03-28 12:22         ` Daniel Jacobowitz
2002-03-28 11:57     ` Daniel Jacobowitz
2002-03-28 11:58     ` Bernd Schmidt
2002-03-28 12:14       ` David O'Brien
2002-03-28 12:29         ` Bernd Schmidt
2002-03-28 13:26         ` law
2002-04-03  2:57   ` Wolfram Gloger [this message]
2002-03-31  6:48 ` Richard Zidlicky
2002-03-31 12:14 Erik Schnetter

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=200204031037.MAA43176@max.zk-i.med.uni-muenchen.de \
    --to=wolfram.gloger@dent.med.uni-muenchen.de \
    --cc=bernds@redhat.com \
    --cc=gcc@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).