If you have any questions you think should be answered in this document,
please let me know.
- --drepper@cygnus.com
+ --drepper@redhat.com
\f
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
Instruction".
1.19. `make' complains about a missing dlfcn/libdl.so when building
malloc/libmemprof.so. How can I fix this?
+1.20. Which tools should I use for MIPS?
+1.21. Which compiler should I use for powerpc64?
+1.22. `make' fails when running rpcgen the first time,
+ what is going on? How do I fix this?
2. Installation and configuration issues
glibc 2.0.x don't work anymore.
2.31. What happened to the Berkeley DB libraries? Can I still use db
in /etc/nsswitch.conf?
+2.32. What has do be done when upgrading to glibc 2.2?
+2.33. The makefiles want to do a CVS commit.
+2.34. When compiling C++ programs, I get a compilation error in streambuf.h.
+2.35. When recompiling GCC, I get compilation errors in libio.
+2.36. Why shall glibc never get installed on GNU/Linux systems in
+/usr/local?
+2.37. When recompiling GCC, I get compilation errors in libstdc++.
3. Source and binary incompatibilities, and what to do about them
3.13. When using the db-2 library which comes with glibc is used in
the Perl db modules the testsuite is not passed. This did not
happen with db-1, gdbm, or ndbm.
-
-Removed. Does not apply anymore.
3.14. The pow() inline function I get when including <math.h> is broken.
I get segmentation faults when I run the program.
3.15. The sys/sem.h file lacks the definition of `union semun'.
libc5. What can be done?
3.20. Programs compiled with glibc 2.1 can't read db files made with glibc
2.0. What has changed that programs like rpm break?
-
-Removed. Does not apply anymore.
3.21. Autoconf's AC_CHECK_FUNC macro reports that a function exists, but
when I try to use it, it always returns -1 and sets errno to ENOSYS.
3.22. My program segfaults when I call fclose() on the FILE* returned
from setmntent(). Is this a glibc bug?
+3.23. I get "undefined reference to `atexit'"
4. Miscellaneous
4.7. Why do so many programs using math functions fail on my AlphaStation?
4.8. The conversion table for character set XX does not match with
what I expect.
+4.9. How can I find out which version of glibc I am using in the moment?
+4.10. Context switching with setcontext() does not work from within
+ signal handlers.
\f
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
*-*-gnu GNU Hurd
i[3456]86-*-linux-gnu Linux-2.x on Intel
m68k-*-linux-gnu Linux-2.x on Motorola 680x0
- alpha-*-linux-gnu Linux-2.x on DEC Alpha
+ alpha*-*-linux-gnu Linux-2.x on DEC Alpha
powerpc-*-linux-gnu Linux and MkLinux on PowerPC systems
+ powerpc64-*-linux-gnu Linux-2.4+ on 64-bit PowerPC systems
sparc-*-linux-gnu Linux-2.x on SPARC
sparc64-*-linux-gnu Linux-2.x on UltraSPARC
arm-*-none ARM standalone systems
arm-*-linux Linux-2.x on ARM
arm-*-linuxaout Linux-2.x on ARM using a.out binaries
+ mips*-*-linux-gnu Linux-2.x on MIPS
+ ia64-*-linux-gnu Linux-2.x on ia64
+ s390-*-linux-gnu Linux-2.x on IBM S/390
+ s390x-*-linux-gnu Linux-2.x on IBM S/390 64-bit
+ cris-*-linux-gnu Linux-2.4+ on CRIS
Ports to other Linux platforms are in development, and may in fact work
already, but no one has sent us success reports for them. Currently no
expressed interest.
If you have a system not listed above (or in the `README' file) and you are
-really interested in porting it, contact
+really interested in porting it, see the GNU C Library web pages to learn
+how to start contributing:
- <bug-glibc@gnu.org>
+ http://www.gnu.org/software/libc/resources.html
1.2. What compiler do I need to build GNU libc?
You should always try to use the latest official release. Older versions
may not have all the features GNU libc requires. The current releases of
-egcs (1.0.3 and 1.1.1) should work with the GNU C library (for powerpc see
-question 1.5; for ARM see question 1.6).
-
-While the GNU CC should be able to compile glibc it is nevertheless adviced
-to use EGCS. Comparing the sizes of glibc on Intel compiled with a recent
-EGCS and gcc 2.8.1 shows this:
-
- text data bss dec hex filename
- egcs-2.93.10 862897 15944 12824 891665 d9b11 libc.so
- gcc-2.8.1 959965 16468 12152 988585 f15a9 libc.so
-
-Make up your own decision.
-
-GNU CC versions 2.95 and above are derived from egcs, and they may do even
-better.
+gcc (3.2 or newer) should work with the GNU C library (for MIPS see question 1.20).
Please note that gcc 2.95 and 2.95.x cannot compile glibc on Alpha due to
problems in the complex float support.
{UD} You definitely need GNU make to build GNU libc. No other make
program has the needed functionality.
-We recommend version GNU make version 3.75 or 3.77. Versions before 3.75
-have bugs and/or are missing features. Version 3.76 has bugs which
-appear when building big projects like GNU libc. 3.76.1 appears to work but
-some people have reported problems. If you build GNU make 3.77 from source,
-please read question 4.6 first.
+We recommend version GNU make version 3.79 or newer. Older versions have
+bugs and/or are missing features.
1.4. Do I need a special linker or assembler?
The static library can be compiled with less featureful tools, but lacks key
features such as NSS.
-For Linux or Hurd, you want binutils 2.8.1.0.23, 2.9.1, or 2.9.1.0.15 or
-higher. These are the only versions we've tested and found reliable. Other
-versions after 2.8.1.0.23 may work but we don't recommend them, especially
-not when C++ is involved. Earlier versions do not work at all.
+For Linux or Hurd, you want binutils 2.13 or higher. These are the only
+versions we've tested and found reliable. Other versions may work but we
+don't recommend them, especially not when C++ is involved.
Other operating systems may come with system tools that have all the
necessary features, but this is moot because glibc hasn't been ported to
1.5. Which compiler should I use for powerpc?
-{GK} You want to use at least gcc 2.95 (together with the right versions
-of all the other tools, of course). See also question question 2.8.
+{} Removed. Does not apply anymore.
1.6. Which tools should I use for ARM?
-{PB} You should use egcs 1.1 or a later version. For ELF systems some
-changes are needed to the compiler; a patch against egcs-1.1.x can be found
-at:
-
-<ftp://ftp.netwinder.org/users/p/philb/egcs-1.1.1pre2-diff-981126>
-
-Binutils 2.9.1.0.16 or later is also required.
+{} Removed. Does not apply anymore.
1.7. Do I need some more things to compile the GNU C Library?
`message catalog' files containing translated versions of system
messages. See ftp://ftp.gnu.org/pub/gnu or better any mirror
site. (We distribute compiled message catalogs, but they may not be
- updated in patches.) Please note that the required minimal version
- (0.10.35) of gettext is alpha software and available from
- ftp://alpha.gnu.org/gnu .
+ updated in patches.)
* Some files are built with special tools. E.g., files ending in .gperf
need a `gperf' program. The GNU version (now available in a separate
* lots of disk space (~400MB for i?86-linux; more for RISC platforms).
* plenty of time. Compiling just the shared and static libraries for
- i?86-linux takes approximately 1h on an AMD-K6@225MHz w/ 96MB of RAM,
- 45mins on a Celeron@400MHz w/ 128MB, and 55mins on a Alpha@533MHz w/ 256MB.
- Multiply this by 1.5 or 2.0 if you build profiling and/or the highly
- optimized version as well. For Hurd systems times are much higher.
+ 35mins on a 2xPIII@550Mhz w/ 512MB RAM. On a 2xUltraSPARC-II@360Mhz
+ w/ 1GB RAM it takes about 14 minutes. Multiply this by 1.5 or 2.0
+ if you build profiling and/or the highly optimized version as well.
+ For Hurd systems times are much higher.
You should avoid compiling in a NFS mounted filesystem. This is
very slow.
- James Troup <J.J.Troup@comp.brad.ac.uk> reports a compile time of
- 45h34m for a full build (shared, static, and profiled) on Atari
- Falcon (Motorola 68030 @ 16 Mhz, 14 Mb memory) and Jan Barte
- <yann@plato.uni-paderborn.de> reports 22h48m on Atari TT030
- (Motorola 68030 @ 32 Mhz, 34 Mb memory)
+ James Troup <J.J.Troup@comp.brad.ac.uk> reports a compile time for
+ an earlier (and smaller!) version of glibc of 45h34m for a full build
+ (shared, static, and profiled) on Atari Falcon (Motorola 68030 @ 16 Mhz,
+ 14 Mb memory) and Jan Barte <yann@plato.uni-paderborn.de> reports
+ 22h48m on Atari TT030 (Motorola 68030 @ 32 Mhz, 34 Mb memory)
A full build of the PowerPC library took 1h on a PowerPC 750@400Mhz w/
64MB of RAM, and about 9h on a 601@60Mhz w/ 72Mb.
- If you have some more measurements let me know.
-
1.8. What version of the Linux kernel headers should be used?
1.9. The compiler hangs while building iconvdata modules. What's
wrong?
-{ZW} This is a problem with old versions of GCC. Initialization of large
-static arrays is very slow. The compiler will eventually finish; give it
-time.
-
-The problem is fixed in egcs 1.1.
+{} Removed. Does not apply anymore.
1.10. When I run `nm -u libc.so' on the produced library I still
1.11. What are these `add-ons'?
{UD} To avoid complications with export rules or external source code some
-optional parts of the libc are distributed as separate packages (e.g., the
-crypt package, see question 2.5).
+optional parts of the libc are distributed as separate packages, e.g., the
+linuxthreads package.
To use these packages as part of GNU libc, just unpack the tarfiles in the
libc source directory and tell the configuration script about them using the
it doesn't, or if you want to select only a subset of the add-ons, give a
comma-separated list of the add-ons to enable:
- configure --enable-add-ons=crypt,linuxthreads
+ configure --enable-add-ons=linuxthreads
for example.
must be written to get everything running.
Most add-ons are tightly coupled to a specific GNU libc version. Please
-check that the add-ons work with the GNU libc. For example the crypt and
-linuxthreads add-ons have the same numbering scheme as the libc and will in
-general only work with the corresponding libc.
+check that the add-ons work with the GNU libc. For example the linuxthreads
+add-on has the same numbering scheme as the libc and will in general only
+work with the corresponding libc.
+
+{AJ} With glibc 2.2 the crypt add-on and with glibc 2.1 the localedata
+add-on have been integrated into the normal glibc distribution, crypt and
+localedata are therefore not anymore add-ons.
1.12. My XXX kernel emulates a floating-point coprocessor for me.
There are some failures which are not directly related to the GNU libc:
- Some compilers produce buggy code. No compiler gets single precision
- complex numbers correct on Alpha. Otherwise, the egcs 1.1 release should be
- ok; gcc 2.8.1 might cause some failures; gcc 2.7.2.x is so buggy that
- explicit checks have been used so that you can't build with it.
+ complex numbers correct on Alpha. Otherwise, gcc-3.2 should be ok.
- The kernel might have bugs. For example on Linux/Alpha 2.0.34 the
floating point handling has quite a number of bugs and therefore most of
the test cases in the math subdirectory will fail. Linux 2.2 has
malloc/libmemprof.so. How can I fix this?
{AJ} Older make version (<= 3.78.90) have a bug which was hidden by a bug in
-glibc (<= 2.1.2). You need to upgrade make to a newer or fixed version. A
-patch is available via
-<http://sourceware.cygnus.com//ml/libc-alpha/2000-02/msg00067.html>.
+glibc (<= 2.1.2). You need to upgrade make to a newer or fixed version.
After upgrading make, you should remove the file sysd-sorted in your build
directory. The problem is that the broken make creates a wrong order for
which happens if you remove the file.
You might encounter this bug also in other situations where make scans
-directories. I strongly advise to upgrade your make version.
+directories. I strongly advise to upgrade your make version to 3.79 or
+newer.
+
+
+1.20. Which tools should I use for MIPS?
+
+{AJ} You should use the current development version of gcc 3.2 or newer from
+CVS.
+
+You need also recent binutils, anything before and including 2.11 will not
+work correctly. Either try the Linux binutils 2.11.90.0.5 from HJ Lu or the
+current development version of binutils from CVS.
+
+Please note that `make check' might fail for a number of the math tests
+because of problems of the FPU emulation in the Linux kernel (the MIPS FPU
+doesn't handle all cases and needs help from the kernel).
+
+For details check also my page <http://www.suse.de/~aj/glibc-mips.html>.
+
+
+1.21. Which compiler should I use for powerpc64?
+
+{SM} You want to use at least gcc 3.2 (together with the right versions
+of all the other tools, of course).
+
+
+1.22. `make' fails when running rpcgen the first time,
+ what is going on? How do I fix this?
+
+{CO} The first invocation of rpcgen is also the first use of the recently
+compiled dynamic loader. If there is any problem with the dynamic loader
+it will more than likely fail to run rpcgen properly. This could be due to
+any number of problems.
+
+The only real solution is to debug the loader and determine the problem
+yourself. Please remember that for each architecture there may be various
+patches required to get glibc HEAD into a runnable state. The best course
+of action is to determine if you have all the required patches.
\f
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
`crypt' and `setkey'. Why aren't these functions in the
libc anymore?
-{UD} The US places restrictions on exporting cryptographic programs and
-source code. Until this law gets abolished we cannot ship the cryptographic
-functions together with glibc.
-
-The functions are available, as an add-on (see question 1.11). People in the US
-may get it from the same place they got GNU libc from. People outside the
-US should get the code from ftp.gwdg.de [134.76.11.100] in the directory
-pub/linux/glibc, or another archive site outside the USA. The README explains
-how to install the sources.
-
-If you already have the crypt code on your system the reason for the failure
-is probably that you did not link with -lcrypt. The crypto functions are in
-a separate library to make it possible to export GNU libc binaries from the
-US.
+{} Removed. Does not apply anymore.
2.6. When I use GNU libc on my Linux system by linking against
glibc 2.x?
{AJ} There's only correct support for glibc 2.0.x in gcc 2.7.2.3 or later.
-But you should get at least gcc 2.8.1 or egcs 1.1 (or later versions)
-instead.
+But you should get at least gcc 2.95.3 (or later versions) anyway
2.10. The `gencat' utility cannot process the catalog sources which
-----------------------------------------------------------------------
# Change catalog source in Linux specific format to standard XPG format.
-# Ulrich Drepper <drepper@cygnus.com>, 1996.
+# Ulrich Drepper <drepper@redhat.com>, 1996.
#
/^\$ #/ {
h
`db-Makefile' in the subdirectory `nss' and you can call it with `make -f
db-Makefile'. Please note that not all services are capable of using a
database. Currently passwd, group, ethers, protocol, rpc, services shadow
-and netgroup are implemented. See also question question 2.31.
+and netgroup are implemented. See also question 2.31.
2.17. I have /usr/include/net and /usr/include/scsi as symlinks
(change /etc/nsswitch.conf for this). You need to link explicitly against
all these services. For example:
- gcc -static test-netdb.c -o test-netdb.c \
- -lc -lnss_files -lnss_dns -lresolv
+ gcc -static test-netdb.c -o test-netdb \
+ -Wl,--start-group -lc -lnss_files -lnss_dns -lresolv -Wl,--end-group
The problem with this approach is that you've got to link every static
program that uses NSS routines with all those libraries.
(that's the name from db 2.4.14 which comes with glibc 2.1.x) and
"libdb-3.0.so" (the name used by db 3.0.55 as default).
+The nss_db module is now in a separate package since it requires a database
+library being available.
+
+
+2.32. What has do be done when upgrading to glibc 2.2?
+
+{AJ} The upgrade to glibc 2.2 should run smoothly, there's in general no
+need to recompile programs or libraries. Nevertheless, some changes might
+be needed after upgrading:
+- The utmp daemon has been removed and is not supported by glibc anymore.
+ If it has been in use, it should be switched off.
+- Programs using IPv6 have to be recompiled due to incompatible changes in
+ sockaddr_in6 by the IPv6 working group.
+- The Berkeley db libraries have been removed (for details see question 2.31).
+- The format of the locale files has changed, all locales should be
+ regenerated with localedef. All statically linked applications which use
+ i18n should be recompiled, otherwise they'll not be localized.
+- glibc comes with a number of new applications. For example ldconfig has
+ been implemented for glibc, the libc5 version of ldconfig is not needed
+ anymore.
+- There's no more K&R compatibility in the glibc headers. The GNU C library
+ requires a C compiler that handles especially prototypes correctly.
+ Especially gcc -traditional will not work with glibc headers.
+
+Please read also the NEWS file which is the authoritative source for this
+and gives more details for some topics.
+
+
+2.33. The makefiles want to do a CVS commit.
+
+{UD} Only if you are not specifying the --without-cvs flag at configure
+time. This is what you always have to use if you are checking sources
+directly out of the public CVS repository or you have your own private
+repository.
+
+
+2.34. When compiling C++ programs, I get a compilation error in streambuf.h.
+
+{BH} You are using g++ 2.95.2? After upgrading to glibc 2.2, you need to
+apply a patch to the include files in /usr/include/g++, because the fpos_t
+type has changed in glibc 2.2. The patch is at
+
+ http://www.haible.de/bruno/gccinclude-glibc-2.2-compat.diff
+
+
+2.35. When recompiling GCC, I get compilation errors in libio.
+
+{BH} You are trying to recompile gcc 2.95.2? Use gcc 2.95.3 instead.
+This version is needed because the fpos_t type and a few libio internals
+have changed in glibc 2.2, and gcc 2.95.3 contains a corresponding patch.
+
+
+2.36. Why shall glibc never get installed on GNU/Linux systems in
+/usr/local?
+
+{AJ} The GNU C compiler treats /usr/local/include and /usr/local/lib in a
+special way, these directories will be searched before the system
+directories. Since on GNU/Linux the system directories /usr/include and
+/usr/lib contain a --- possibly different --- version of glibc and mixing
+certain files from different glibc installations is not supported and will
+break, you risk breaking your complete system. If you want to test a glibc
+installation, use another directory as argument to --prefix. If you like to
+install this glibc version as default version, overriding the existing one,
+use --prefix=/usr and everything will go in the right places.
+
+
+2.37. When recompiling GCC, I get compilation errors in libstdc++.
+
+{BH} You are trying to recompile gcc 3.2? You need to patch gcc 3.2,
+because some last minute changes were made in glibc 2.3 which were not
+known when gcc 3.2 was released. The patch is at
+
+ http://www.haible.de/bruno/gcc-3.2-glibc-2.3-compat.diff
+
\f
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
but this is what a major release is for. It's better to have a cut now than
having no means to support the new techniques later.
-{MK} There is however a (partial) solution for this problem. Please take a
-look at the file `login/README.utmpd'.
-
3.3. Where are the DST_* constants found in <sys/time.h> on many
systems?
the Perl db modules the testsuite is not passed. This did not
happen with db-1, gdbm, or ndbm.
-Removed. Does not apply anymore.
-
-
+{} Removed. Does not apply anymore.
3.14. The pow() inline function I get when including <math.h> is broken.
3.20. Programs compiled with glibc 2.1 can't read db files made with glibc
2.0. What has changed that programs like rpm break?
-Removed. Does not apply anymore.
-
-
+{} Removed. Does not apply anymore.
3.21. Autoconf's AC_CHECK_FUNC macro reports that a function exists, but
won't always work. Unfortunately, for compatibility reasons, we can't
change the return type of setmntent() to something other than FILE *.
+
+3.23. I get "undefined reference to `atexit'"
+
+{UD} This means that your installation is somehow broken. The situation is
+the same as for 'stat', 'fstat', etc (see question 2.7). Investigate why the
+linker does not pick up libc_nonshared.a.
+
+If a similar message is issued at runtime this means that the application or
+DSO is not linked against libc. This can cause problems since 'atexit' is
+not exported anymore.
+
\f
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
kernel for IPv6 is 2.1.129.
Also, as of the 2.1 release the IPv6 API provided by GNU libc is not
-100% complete. In particular the getipnodebyname and getipnodebyaddr
-functions are not implemented.
+100% complete.
4.3. When I set the timezone by setting the TZ environment variable
4.6. I've build make 3.77 against glibc 2.1 and now make gets
segmentation faults.
-{AJ} GNU make 3.77 has support for 64 bit filesystems which is slightly
-broken (and one of the new features in the GNU C library 2.1 is 64 bit
-filesystem support :-( ). To get a working make you can use either make
-3.75 or patch 3.77. A working patch is available via RedHat's Rawhide server
-(ftp://rawhide.redhat.com/SRPMS/SRPMS/make-3.77-*src.rpm).
+{} Removed. Does not apply anymore, use make 3.79 or newer.
4.7. Why do so many programs using math functions fail on my AlphaStation?
if it cannot directly map a character this is a perfectly good solution
since the semantics and appearance of the character does not change.
+
+4.9. How can I find out which version of glibc I am using in the moment?
+
+{UD} If you want to find out about the version from the command line simply
+run the libc binary. This is probably not possible on all platforms but
+where it is simply locate the libc DSO and start it as an application. On
+Linux like
+
+ /lib/libc.so.6
+
+This will produce all the information you need.
+
+What always will work is to use the API glibc provides. Compile and run the
+following little program to get the version information:
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+#include <stdio.h>
+#include <gnu/libc-version.h>
+int main (void) { puts (gnu_get_libc_version ()); return 0; }
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+This interface can also obviously be used to perform tests at runtime if
+this should be necessary.
+
+
+4.10. Context switching with setcontext() does not work from within
+ signal handlers.
+
+{DMT} The Linux implementations (IA-64, S390 so far) of setcontext()
+supports synchronous context switches only. There are several reasons for
+this:
+
+- UNIX provides no other (portable) way of effecting a synchronous
+ context switch (also known as co-routine switch). Some versions
+ support this via setjmp()/longjmp() but this does not work
+ universally.
+
+- As defined by the UNIX '98 standard, the only way setcontext()
+ could trigger an asychronous context switch is if this function
+ were invoked on the ucontext_t pointer passed as the third argument
+ to a signal handler. But according to draft 5, XPG6, XBD 2.4.3,
+ setcontext() is not among the set of routines that may be called
+ from a signal handler.
+
+- If setcontext() were to be used for asynchronous context switches,
+ all kinds of synchronization and re-entrancy issues could arise and
+ these problems have already been solved by real multi-threading
+ libraries (e.g., POSIX threads or Linux threads).
+
+- Synchronous context switching can be implemented entirely in
+ user-level and less state needs to be saved/restored than for an
+ asynchronous context switch. It is therefore useful to distinguish
+ between the two types of context switches. Indeed, some
+ application vendors are known to use setcontext() to implement
+ co-routines on top of normal (heavier-weight) pre-emptable threads.
+
+It should be noted that if someone was dead-bent on using setcontext()
+on the third arg of a signal handler, then IA-64 Linux could support
+this via a special version of sigaction() which arranges that all
+signal handlers start executing in a shim function which takes care of
+saving the preserved registers before calling the real signal handler
+and restoring them afterwards. In other words, we could provide a
+compatibility layer which would support setcontext() for asynchronous
+context switches. However, given the arguments above, I don't think
+that makes sense. setcontext() provides a decent co-routine interface
+and we should just discourage any asynchronous use (which just calls
+for trouble at any rate).
+
\f
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
Answers were given by:
-{UD} Ulrich Drepper, <drepper@cygnus.com>
-{DMT} David Mosberger-Tang, <davidm@AZStarNet.com>
+{UD} Ulrich Drepper, <drepper@redhat.com>
+{DMT} David Mosberger-Tang, <davidm@hpl.hp.com>
{RM} Roland McGrath, <roland@gnu.org>
{AJ} Andreas Jaeger, <aj@suse.de>
{EY} Eric Youngdale, <eric@andante.jic.com>
{MK} Mark Kettenis, <kettenis@phys.uva.nl>
{ZW} Zack Weinberg, <zack@rabi.phys.columbia.edu>
{TK} Thorsten Kukuk, <kukuk@suse.de>
-{GK} Geoffrey Keating, <geoffk@ozemail.com.au>
+{GK} Geoffrey Keating, <geoffk@redhat.com>
{HJ} H.J. Lu, <hjl@gnu.org>
{CG} Cristian Gafton, <gafton@redhat.com>
-{AO} Alexandre Oliva, <oliva@lsd.ic.unicamp.br>
+{AO} Alexandre Oliva, <aoliva@redhat.com>
+{BH} Bruno Haible, <haible@clisp.cons.org>
+{SM} Steven Munroe, <sjmunroe@us.ibm.com>
\f
Local Variables:
mode:outline
projects / platform / upstream / glibc.git / blobdiff