Re: libio patches for glibc 2.1

[Jeffrey A Law <law at cygnus dot com>]

  In message <m0y71JM-00058gC@ocean.lucon.org>you write:
  > > 
  > > 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.
  > > 
  > > 
  > > 1998-02-22  Andreas Schwab  <schwab@issan.informatik.uni-dortmund.de>
  > > 
  > > 	Changes for _G_IO_IO_FILE_VERSION == 0x20001:
  > > 	* libioP.h (_IO_showmanyc_t, _IO_SHOWMANYC, _IO_imbue_t,
  > > 	_IO_IMBUE): New definitions.
  > > 	(struct _IO_jump_t): Add __showmanyc and __imbue fields.
  > > 	(_IO_file_fopen): Add new fourth argument.
  > > 	* filebuf.cc (filebuf::open): Pass new fourth argument to
  > > 	_IO_file_fopen.
  > > 	* iolibio.h (_IO_freopen): Likewise.
  > > 	* streambuf.cc (streambuf::showmanyc, streambuf::imbue): New
  > > 	functions.
  > > 	* streambuf.h (_IO_wchar_t): Define to _G_wchar_t.
  > > 	(ios::fill): Remove casts.
  > > 	(struct streambuf): Add showmanyc and imbue members.
  > > 
  > > 	* iostream.cc (ostream::operator<<(double n)) [__GLIBC_MINOR__ >=
  > > 	1]: Initialize new fields is_char of struct printf_info.
  > > 	(ostream::operator<<(long double n)) [__GLIBC_MINOR__ >= 1]:
  > > 	Likewise.
  > 
  > Ulrich, should this also go into egcs 1.0.2?
I installed this on the release branch too.

At this point I'd like to change modes -- we've installed far more
patches than I would have liked for this release.  I'd like to get
patches for two more problems, then call the release sources frozen
except for end-of-the-world bugs and the usual doc updates so that
we can get the release tested!

We need patches for:

    * -Di386 lossage.  I think we decided to go ahead and define
    i386, except with -ansi is in effect.  Can someone provide a
    patch for this?

    * A fix for the sigset_t problem.  I've got no opinion on what
    the best fix is -- I'm depending on y'all to make that technical
    decision.    



I'm offline March 11 - March 15.  Having the release ready to go by
March 11 would be best.  I might be able to swing March 15 or 16,
but if we go beyond those dates we'll have to push the release into
April due to EOQ concerns at Cygnus.