From: hjl@lucon.org (H.J. Lu)
To: drepper@cygnus.com
Cc: schwab@issan.informatik.uni-dortmund.de, egcs@cygnus.com
Subject: Re: libio patches for glibc 2.1
Date: Mon, 23 Feb 1998 11:54:00 -0000 [thread overview]
Message-ID: <m0y71y0-00058gC@ocean.lucon.org> (raw)
In-Reply-To: <r23ehafcn7.fsf@happy.cygnus.com>
>
> hjl@lucon.org (H.J. Lu) writes:
>
> > >
> > > This patch fixes some problems in libio in connection with glibc 2.1.
> > > Note that the change of _IO_wchar_t is a binary incompatibility, so users
> > > of glibc 2.1 snapshots need to recompile at least all code that uses
> > > [io]fstream.
> > > [...]
> > Ulrich, should this also go into egcs 1.0.2?
>
> I think we should leave it out especially since Jeff plans to have
> egcs 1.1 in the not too far future and people who really use glibc 2.1
> these days can also use the egcs snapshots (instead of the final 1.0
> release).
>
RedHat, Debian and SuSE may want to use egcs 1.0.x for glibc 2.1 even
if egcs 1.1 is released.
BTW, the current egcs snapshots change a lot. I am using egcs 1.0.x
for glibc 2.1. I don't want to guess which one is at fault, egcs
or glibc, when something goes wrong.
--
H.J. Lu (hjl@gnu.org)
next prev parent reply other threads:[~1998-02-23 11:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-23 2:16 Andreas Schwab
1998-02-23 11:54 ` H.J. Lu
1998-02-23 11:54 ` Ulrich Drepper
1998-02-23 11:54 ` H.J. Lu [this message]
1998-02-23 11:00 ` Ulrich Drepper
1998-02-23 11:00 ` H.J. Lu
1998-02-23 11:54 ` Ulrich Drepper
1998-02-23 13:07 ` H.J. Lu
1998-02-23 14:09 ` Joe Buck
1998-02-23 15:08 ` Ulrich Drepper
1998-02-23 15:08 ` Joe Buck
1998-02-23 15:24 ` Ulrich Drepper
1998-02-23 15:31 ` Joe Buck
1998-02-23 15:34 ` Ulrich Drepper
1998-02-24 3:09 ` Jeffrey A Law
1998-02-25 9:33 ` Jeffrey A Law
1998-02-25 11:32 ` H.J. Lu
[not found] ` <1949.888379825.cygnus.egcs@hurl.cygnus.com>
1998-02-25 11:32 ` Jason Merrill
1998-02-25 19:12 ` H.J. Lu
1998-02-25 20:56 ` Jason Merrill
1998-03-05 16:38 ` H.J. Lu
1998-02-26 20:35 ` Robert Wilhelm
1998-03-05 16:38 ` H.J. Lu
1998-02-25 9:33 ` Jeffrey A Law
1998-02-23 15:57 Mike Stump
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=m0y71y0-00058gC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=drepper@cygnus.com \
--cc=egcs@cygnus.com \
--cc=schwab@issan.informatik.uni-dortmund.de \
/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).