diff options
Diffstat (limited to 'FAQ.in')
| -rw-r--r-- | FAQ.in | 30 |
1 files changed, 11 insertions, 19 deletions
diff --git a/FAQ.in b/FAQ.in index 348a8607cd..d010ef8e93 100644 --- a/FAQ.in +++ b/FAQ.in @@ -217,8 +217,8 @@ errors while linking before deciding there is a problem. ??addon 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 ?crypt). +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 @@ -227,7 +227,7 @@ to find all the add-on packages in your source tree. This may not work. If 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. @@ -237,9 +237,13 @@ else. The existing makefiles do most of the work; only some few stub rules 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. ?? My XXX kernel emulates a floating-point coprocessor for me. Should I enable --with-fp? @@ -472,20 +476,8 @@ versions of some string functions. These can only be used with GCC. See `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 ?addon). 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. ?? When I use GNU libc on my Linux system by linking against the libc.so which comes with glibc all I get is a core dump. |