From: Petr Baudis <pasky@suse.cz>
To: info-gnu@gnu.org, libc-announce@sourceware.org,
libc-alpha@sourceware.org
Subject: glibc-2.11.1 released
Date: Mon, 04 Jan 2010 14:08:00 -0000 [thread overview]
Message-ID: <20091229162437.GE2249@machine.or.cz> (raw)
[-- Attachment #1: Type: text/plain, Size: 1922 bytes --]
Hello!
Apologies for the late announcement long after the tag has been created,
I have been stuck on obtaining the necessary upload permissions first
and then I was not available over the holidays. The homepage will
hopefully be updated shortly. Anyway:
This is a bugfix glibc release, revising the glibc-2.11 release only
by bugfixes backported from the master glibc development branch.
The following known significant bugs exist in this release:
* Empty /etc/resolv.conf incorrectly does not cause glibc to default
to localhost, to solve this issue please apply one of the patches in:
http://sourceware.org/bugzilla/show_bug.cgi?id=10851
These commits were included since glibc-2.11:
Andreas Schwab (1):
Fix infloop in __pthread_disable_asynccancel on x86_64
H.J. Lu (1):
Properly recover from shorter read.
Jakub Jelinek (1):
Fix sync_file_range on ppc/ppc64.
Mike Frysinger (3):
Add missing stdio.h include.
Fix building on x86 with older kernel headers.
Missing CL.
Paolo Bonzini (1):
Fix ranges with multibyte characters as endpoints.
Petr Baudis (1):
glibc 2.11.1 release
Ulrich Drepper (15):
Fix F_SETOWN_EX and F_GETOWN_EX definitions.
Add missing Linux MADV_* definitions.
Fix _NC_LOCALE_NAME definition.
Handle LC_GLOBAL_LOCALE in duplocale.
Add missing test files.
Whitespace fixes.
Avoid warnings in CPU_* macros when using const bitsets.
Fix getwc* and putwc* on non-wide streams.
Reinitialize _create_xid state after fork.
Fix week information for nl_NL locale.
Define week, first_weekday, and first_workday for en_DK locale.
Define week, first_weekday, and first_workday for hsb_DE locale.
Fix startup to security-relevant statically linked binaries.
Prevent unintended file desriptor leak in grantpt.
Avoid local PLTs.
Enjoy!
Petr "Pasky" Baudis
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
reply other threads:[~2010-01-04 14:08 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=20091229162437.GE2249@machine.or.cz \
--to=pasky@suse.cz \
--cc=info-gnu@gnu.org \
--cc=libc-alpha@sourceware.org \
--cc=libc-announce@sourceware.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).