From: Ulrich Drepper <drepper@redhat.com>
To: GNU libc devel <libc-alpha@sources.redhat.com>,
linux-gcc@vger.kernel.org
Subject: glibc 2.3.1
Date: Thu, 10 Oct 2002 23:40:10 -0700 [thread overview]
Message-ID: <3DA6724A.2030705@redhat.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I've uploaded
glibc-2.3.1.tar.bz2
glibc-2.3-2.3.1.diff.bz2
glibc-2.3.1pre2-2.3.1.diff.bz2
glibc-linuxthreads-2.3.1.tar.bz2
to
ftp://sources.redhat.com/pub/glibc/releases/
The files will soon also be available at
ftp://ftp.gnu.org/pub/gnu/glibc/
and the mirrors worldwide.
This releases is mainly meant to introduce some changes which work
around problems some programs have which use very small stack sizes and
still expect all libc functions to be usable. Beside this change only
very few, mostly non-code, changes are included. Every user of glibc
2.3 should upgrade.
As usual, compiling glibc is nothing for the faint hearted. It is
complicated and demanding and can potentially ruin your entire
installation. Better wait for your distribution maker to provide you
with binaries. People who nevertheless compile glibc on their own have
to read the documentation, FAQ, and the announcement for the 2.3 release:
http://sources.redhat.com/ml/libc-alpha/2002-10/msg00048.html
- --
- --------------. ,-. 444 Castro Street
Ulrich Drepper \ ,-----------------' \ Mountain View, CA 94041 USA
Red Hat `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE9pnJO2ijCOnn/RHQRAuYNAJ4+0tsi9Iq55RB7iPpndhnSTPFB1QCfZD8y
l14J4/l63KWOZbwKG375hTs=
=YIW3
-----END PGP SIGNATURE-----
next reply other threads:[~2002-10-11 6:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-11 6:40 Ulrich Drepper [this message]
2003-01-04 1:13 ` glibc 2.3.1 [PATCH] sysdeps/i386/i486/bits/string.h Denis Zaitsev
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=3DA6724A.2030705@redhat.com \
--to=drepper@redhat.com \
--cc=libc-alpha@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).