public inbox for libc-announce@sourceware.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: libc-announce@sources.redhat.com, libc-alpha@sources.redhat.com,
	VGER gcc list <linux-gcc@vger.kernel.org>
Subject: glibc 2.2.5
Date: Sun, 20 Jan 2002 22:56:00 -0000	[thread overview]
Message-ID: <m3ofjow6e9.fsf@myware.mynet> (raw)

I've uploaded the files

  glibc-2.2.5.tar.bz2               (also .gz)
  glibc-linuxthreads-2.2.5.tar.bz2  (also .gz)
  glibc-2.2.4-2.2.5.diff.bz2        (also .gz)
  glibc-2.2.5pre1-2.2.5.diff.bz2    (also .gz)

to

  ftp://sources.redhat.com/pub/glibc/releases/

The files will shortly appear on

  ftp://ftp.gnu.org/pub/gnu/glibc/

and all the mirrors (of both servers) world-wide.  Please use mirrors
if possible.

The user visible changes in this release include:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Version 2.2.5

* Stephen Moshier implemented log2, log10, powl and cbrtl for the
  128-bit long double format.

* Masahide Washizawa contributed iconv modules for IBM1132, IBM1133, IBM1160,
  IBM1161, and IBM1162 charsets.

* Andreas Jaeger contributed a port to x86-64/Linux.

* Peter Bruin contributed a port to PowerPC/Hurd.

* libc functions using I/O streams now can handle wide-oriented streams
  as well.

* optimizations in the dynamic linker.  Binaries created by recent binutils
  versions start up quicker due to reduced time spend on relocations.

* Support for use of gcc3 added by Jakub Jelinek and HJ Lu.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Despite this short list the changes are quite long and complicated.
The dynamic linker change as well as the gcc3 support are quite
complicated and potentially carry the risk of problems.  But we don't
expect any problems and therefore upgrading to version is advised.
Installation is not easy and has the potential to ruin your system.
Therefore it is highly encouraged to use the packages provided by the
distribution maker once they become available.

The release has been tested and no big problems were reported.  Only
on Alpha one of the tests (reldep6 in elf/) fails due to a bug in the
binutils.  No solution exists for this at this point so just ignore
the problem for now.

If no dangerous problems are found this will be the last release in
the 2.2 series.  Work on 2.3 is already on the way and all efforts are
concentrated on this.


As usual, I couldn't have done the work alone.  The usual crowd is
responsible and deserves thanks:

	Wolfram Gloger
	Bruno Haible
	Richard Henderson
	Andreas Jaeger
	Jakub Jelinek
	Thorsten Kukuk
	Kaz Kylheku
	H.J. Lu
	Roland McGrath
	Stephen L Moshier
	Andreas Schwab
	Masahide Washizawa

plus many more who send reports and patches.

-- 
---------------.                          ,-.   1325 Chesapeake Terrace
Ulrich Drepper  \    ,-------------------'   \  Sunnyvale, CA 94089 USA
Red Hat          `--' drepper at redhat.com   `------------------------

                 reply	other threads:[~2002-01-21  6:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=m3ofjow6e9.fsf@myware.mynet \
    --to=drepper@redhat.com \
    --cc=libc-alpha@sources.redhat.com \
    --cc=libc-announce@sources.redhat.com \
    --cc=linux-gcc@vger.kernel.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).