I've packaged current glibc git version (release planned before
Christmas) and like to submit it to Factory now - and update it until
the release.
Looking at the changes, we receive a lot of bugfixes but I'm not aware of
any expected breakage due to it.
Coolo, do you want to setup a staging project first or shall I submit via
Base:System to Factory directly?
The package is building in my project home:a_jaeger:devel-glibc right
now.
Andreas
P.S. The NEWS file lists these changes:
* Bugfixes
* Port to ARM AArch64 contributed by Linaro.
* Support for STT_GNU_IFUNC symbols added for s390 and s390x.
Optimized versions of memcpy, memset, and memcmp added for System z10
and
zEnterprise z196.
Implemented by Andreas Krebbel.
* The new function secure_getenv allows secure access to the
environment,
returning NULL if running in a SUID/SGID process. This function
replaces
the internal function __secure_getenv.
* SystemTap static probes have been added into the dynamic linker.
Implemented by Gary Benson.
* Optimizations of string functions strstr, strcasestr and memmem.
Implemented by Maxim Kuvyrkov.
* The minimum Linux kernel version that this version of the GNU C
Library
can be used with is 2.6.16.
* Optimizations of string functions memchr, wcschr, wcscpy, and wcsrchr
for
powerpc POWER7. Implemented by Will Schmidt.
* New configure option --disable-nscd builds the C library such that it
never attempts to contact the Name Service Caching Daemon (nscd).
New configure option --disable-build-nscd avoids building nscd itself;
this is the default if --disable-nscd is used.
* The ttyname and ttyname_r functions on Linux now fall back to
searching for
the tty file descriptor in /dev/pts or /dev if /proc is not available.
This
allows creation of chroots without the procfs mounted on /proc.
* The `crypt' function now fails if passed salt bytes that violate the
specification for those values. On Linux, the `crypt' function will
consult /proc/sys/crypto/fips_enabled to determine if "FIPS mode" is
enabled, and fail on encrypted strings using the MD5 or DES algorithm
when the mode is enabled.
* The `clock_*' suite of functions (declared in