Tue May 28 04:38:10 1996 Ulrich Drepper <drepper@cygnus.com>

	* limits.h: Change MB_LEN_MAX to 6.  A 31-bit ISO 10646
	character in UTF-8 encoding has that many bytes.

	* locale/langinfo.h: New element _NL_CTYPE_MB_CUR_MAX.
	* locale/categories.def: Add description of field _NL_CTYPE_MB_CUR_MAX.
	* locale/Makefile (routines): Add mb_cur_max.
	* locale/mb_cur_max.c: New file.  This function gets called
	when the macro MB_CUR_MAX is used.
	* locale/C-ctype.c: Initialize new mb_cur_max field.
	* locale/localeinfo.h: Change magic value because of incompatible
        change.
	* locale/programs/ld-ctype.c: Determine value of mb_cur_max
        according to current character set and write it out with the rest.
	* stdlib/stdlib.h (MB_CUR_MAX): Not constant anymore.  Get value
        according to currently used locale for catefory LC_CTYPE by
        calling the function __ctype_get_mb_cur_max.

Tue May 28 03:27:46 1996  Ulrich Drepper  <drepper@cygnus.com>

	* FAQ:  Fix some typos.
	Tell that for Linux the kernel header files are necessary.

	* PROJECTS: New file.  List of open jobs for glibc.
	* Makefile (distribute): Add PROJECTS.

	* crypt/GNUmakefile (headers): New variable.  Mention crypt.h.
	* crypt/crypt.h: Header for crypt functions.

	* elf/elf.h: Add some new constants from recent Cygnus ELF
	header files.

	* login/getutid_r.c: Test for correct type.
	Don't depend on ut_type and ut_id unless _HAVE_UT_TYPE and
	_HAVE_UT_ID resp. are defined.
	Make really compliant with specification.

	* login/getutline_r.c, login/pututline_r.c: Don't depend on
	ut_type and ut_id unless _HAVE_UT_TYPE and _HAVE_UT_ID resp. are
	defined.
	Make really compliant with specification.

	* login/setutent_r.c: Don't depend on ut_type and ut_id unless
	_HAVE_UT_TYPE and _HAVE_UT_ID resp. are defined.

	* login/login.c, login/logout.c, login/logwtmp.c: Complete
	rewrite.  Now based on getut*/setut* functions.

	* stdlib/strtol.c: Undo changes of Wed May 22 01:48:54 1996.
	This prevented using this file in other GNU packages.

	* sysdeps/gnu/utmpbits.h: Define _HAVE_UT_TYPE, _HAVE_UT_ID,
	and _HAVE_UT_TV because struct utmp has these members.

	* sysdeps/libm-i387/e_exp.S: Correct exp(+-Inf) case.

	* utmp.h: New file.  Wrapper around login/utmp.h.

	* elf/dl-error.c (struct catch): New type.
	(catch): New static variable, struct catch *.
	(catch_env, signalled_errstring, signalled_objname): Variables removed.
	(_dl_signal_error): If CATCH is non-null, set its errstring and
	objname members and jump to CATCH->env.  If it is null, call
	_dl_sysdep_fatal with a standard message.
	* elf/rtld.c (dl_main): Explode `doit' function into dl_main's body.
	No longer use _dl_catch_error.

1 files changed, 23 insertions, 13 deletions

diff --git a/FAQ b/FAQ
index 9ebd95d7a5..f85b255bbc 100644
--- a/FAQ
+++ b/FAQ
@@ -102,8 +102,8 @@ from your favourite mirror of prep.ai.mit.edu.
 ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
 [Q5]	``Do I need a special linker or archiver?''
 
-[A5] {UD} If your native versions are not too buggy you can work with
-them.  But GNU libc works best with GNU binutils.
+[A5] {UD} If your native versions are not too buggy you can probably
+work with them.  But GNU libc works best with GNU binutils.
 
 On systems where the native linker does not support weak symbols you
 will not get a really ISO C compliant C library.  Generally speaking
@@ -119,7 +119,7 @@ Older releases are known to have bugs that affect building the GNU C library.
 
 [A6] {UD} Yes, there are some more :-).
 
-* lots of diskspace (for i386-linux this means, e.g., ~70MB)
+* lots of diskspace (for i386-linux this means, e.g., ~70MB).
 
   You should avoid compiling on a NFS mounted device.  This is very
   slow.
@@ -130,6 +130,12 @@ Older releases are known to have bugs that affect building the GNU C library.
   If you are interested in some more measurements let me know.
 
 
+* When compiling for Linux:
+
+  + the header files of the Linux kernel must be available in the
+    search path of the CPP as <linux/*.h> and <asm/*.h>.
+
+
 ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
 [Q7]	``When I run `nm libc.so|grep " U "' on the produced library
 	  I still find unresolved symbols?  Can this be ok?''
@@ -138,7 +144,7 @@ Older releases are known to have bugs that affect building the GNU C library.
 symbols:
 
 * magic symbols automatically generated by the linker.  Names are
-  often like __start_* and __stop_*-
+  often like __start_* and __stop_*
 
 * symbols resolved by using libgcc.a
   (__udivdi3, __umoddi3, or similar)
@@ -161,14 +167,18 @@ and with cleanliness.  With the introduction of a new version number these
 errors now can be corrected.  Here is a list of the known source code
 incompatibilities:
 
-* _GNU_SOURCE: glibc does not automatically define _GNU_SOURCE.  Thus, if a
-  program depends on GNU extensions, it is necessary to compile it with C
-  compiler option -D_GNU_SOURCE, or better, to put `#define _GNU_SOURCE' at
-  the beginning of your source files, before any C library header files are
-  included.  This difference normally mainfests itself in the form of
-  missing prototypes and/or data type definitions.  Thus, if you get such
-  errors, the first thing you should do is try defining _GNU_SOURCE and see
-  if that makes the problem go away.
+* _GNU_SOURCE: glibc does not automatically define _GNU_SOURCE.  Thus,
+  if a program depends on GNU extensions or some other non-standard
+  functionality, it is necessary to compile it with C compiler option
+  -D_GNU_SOURCE, or better, to put `#define _GNU_SOURCE' at the beginning
+  of your source files, before any C library header files are included.
+  This difference normally manifests itself in the form of missing
+  prototypes and/or data type definitions.  Thus, if you get such errors,
+  the first thing you should do is try defining _GNU_SOURCE and see if
+  that makes the problem go away.
+
+  For more information consult the file `NOTES' part of the GNU C
+  library sources.
 
 * reboot(): GNU libc sanitizes the interface of reboot() to be more
   compatible with the interface used on other OSes.  In particular,
@@ -209,7 +219,7 @@ Answers were given by:
 {DMT} David Mosberger-Tang, <davidm@AZStarNet.com>
 
 Amended by:
-{RM} Roland McGrath <roland@gnu.ai.mit.edu>
+{RM} Roland McGrath, <roland@gnu.ai.mit.edu>
 
 Local Variables:
  mode:text