Regenerated.

1 files changed, 44 insertions, 3 deletions

diff --git a/FAQ b/FAQ
index bfd7fb3..4d6bf76 100644
--- a/FAQ
+++ b/FAQ
@@ -46,6 +46,7 @@ please let me know.
 	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?
 
 2. Installation and configuration issues
 
@@ -114,6 +115,7 @@ Removed.  Does not apply anymore.
 	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?
 
 3. Source and binary incompatibilities, and what to do about them
 
@@ -213,6 +215,7 @@ in the future, are:
 	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
 
 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
@@ -240,7 +243,7 @@ a local mirror first.
 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).
+question 1.5; for ARM see question 1.6; for MIPS see question 1.20).
 
 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
@@ -574,6 +577,18 @@ You might encounter this bug also in other situations where make scans
 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 2.97 from CVS.
+gcc 2.95.x does not work correctly on mips-linux.
+
+You need also recent binutils, anything before and including 2.10 will not
+work correctly.  Either try the Linux binutils 2.10.0.33 from HJ Lu or the
+current development version from CVS of binutils.
+
+For details check also my page <http://www.suse.de/~aj/glibc-mips.html>.
+
 
 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 
 
@@ -1028,8 +1043,8 @@ can create a static binary that will use only the services dns and files
 (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.
@@ -1210,6 +1225,32 @@ Currently the code searches for libraries with a soname of "libdb.so.3"
 (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 ??nssdb).
+- 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.
+
+Please read also the NEWS file which is the authoritative source for this
+and gives more details for some topics.
+
 
 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .