mirror of
https://sourceware.org/git/glibc.git
synced 2025-01-05 01:00:14 +00:00
Remade for stable-2.1
This commit is contained in:
parent
de1703ff95
commit
d24adae5c0
11
INSTALL
11
INSTALL
@ -31,9 +31,8 @@ below.
|
|||||||
Configuring and compiling GNU Libc
|
Configuring and compiling GNU Libc
|
||||||
==================================
|
==================================
|
||||||
|
|
||||||
GNU Libc cannot be compiled in the source directory. You must
|
GNU Libc can be compiled in the source directory but we'd advise to
|
||||||
create a separate directory for the object files. This directory
|
build in a separate build directory. For example, if you have unpacked
|
||||||
should be outside the source tree. For example, if you have unpacked
|
|
||||||
the glibc sources in `/src/gnu/glibc-2.1.0', create a directory
|
the glibc sources in `/src/gnu/glibc-2.1.0', create a directory
|
||||||
`/src/gnu/glibc-build' to put the object files in.
|
`/src/gnu/glibc-build' to put the object files in.
|
||||||
|
|
||||||
@ -226,9 +225,9 @@ file to coexist with new programs. For more information see the files
|
|||||||
permissions on a pseudoterminal so it can be used by the calling
|
permissions on a pseudoterminal so it can be used by the calling
|
||||||
process. This means programs like `xterm' and `screen' do not have to
|
process. This means programs like `xterm' and `screen' do not have to
|
||||||
be setuid to get a pty. (There may be other reasons why they need
|
be setuid to get a pty. (There may be other reasons why they need
|
||||||
privileges.) If you are using a 2.1 Linux kernel with the `devptsfs'
|
privileges.) If you are using a 2.1 or newer Linux kernel with the
|
||||||
or `devfs' filesystems providing pty slaves, you don't need this
|
`devptsfs' or `devfs' filesystems providing pty slaves, you don't need
|
||||||
program; otherwise you do. The source for `pt_chown' is in
|
this program; otherwise you do. The source for `pt_chown' is in
|
||||||
`login/programs/pt_chown.c'.
|
`login/programs/pt_chown.c'.
|
||||||
|
|
||||||
Recommended Tools for Compilation
|
Recommended Tools for Compilation
|
||||||
|
4
README
4
README
@ -1,4 +1,4 @@
|
|||||||
This directory contains the version 2.0.112 test release of the GNU C Library.
|
This directory contains the version 2.1 release of the GNU C Library.
|
||||||
Many bugs have been fixed since the last release.
|
Many bugs have been fixed since the last release.
|
||||||
Some bugs surely remain.
|
Some bugs surely remain.
|
||||||
|
|
||||||
@ -53,7 +53,7 @@ provides the Unix `crypt' function, plus some other entry points.
|
|||||||
Because of the United States export restriction on DES implementations,
|
Because of the United States export restriction on DES implementations,
|
||||||
we are distributing this code separately from the rest of the C
|
we are distributing this code separately from the rest of the C
|
||||||
library. There is an extra distribution tar file just for crypt; it is
|
library. There is an extra distribution tar file just for crypt; it is
|
||||||
called `glibc-crypt-2.0.112.tar.gz'. You can just unpack the crypt
|
called `glibc-crypt-2.1.tar.gz'. You can just unpack the crypt
|
||||||
distribution along with the rest of the C library and build; you can
|
distribution along with the rest of the C library and build; you can
|
||||||
also build the library without getting crypt. Users outside the USA
|
also build the library without getting crypt. Users outside the USA
|
||||||
can get the crypt distribution via anonymous FTP from ftp.ifi.uio.no
|
can get the crypt distribution via anonymous FTP from ftp.ifi.uio.no
|
||||||
|
@ -1,4 +1,4 @@
|
|||||||
This directory contains the version VERSION test release of the GNU C Library.
|
This directory contains the version VERSION release of the GNU C Library.
|
||||||
Many bugs have been fixed since the last release.
|
Many bugs have been fixed since the last release.
|
||||||
Some bugs surely remain.
|
Some bugs surely remain.
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user