qiurui
/
glibc
mirror of git://sourceware.org/git/glibc.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

2004-08-09 Roland McGrath <roland@frob.com> 

* manual/install.texi (Supported Configurations): Replace bug-glibc
	mention with web URL.
	* INSTALL: Regenerated.
	* locale/iso-3166.def: Likewise, in comment.
	* locale/iso-4217.def: Likewise.
	* locale/iso-639.def: Likewise.
	* posix/cpio.h: Remove bug reporting comment.
This commit is contained in:
Roland McGrath 2004-08-10 05:10:38 +00:00
parent 8799d9356a
commit 80ed68b7bc
6 changed files with 63 additions and 62 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

108
INSTALL
View File

@ -1,8 +1,8 @@
Installing the GNU C Library Appendix A Installing the GNU C Library
**************************** ***************************************
Before you do anything else, you should read the file `FAQ' located Before you do anything else, you should read the file `FAQ' located at
at the top level of the source tree. This file answers common questions the top level of the source tree. This file answers common questions
and describes problems you may experience with compilation and and describes problems you may experience with compilation and
installation. It is updated more frequently than this manual. installation. It is updated more frequently than this manual.
@ -23,15 +23,15 @@ bundle; the file is `glibc-linuxthreads-VERSION.tar.gz'.
and GNU Make, and possibly others. *Note Tools for Compilation::, and GNU Make, and possibly others. *Note Tools for Compilation::,
below. below.
Configuring and compiling GNU Libc A.1 Configuring and compiling GNU Libc
================================== ======================================
GNU libc can be compiled in the source directory, but we strongly GNU libc can be compiled in the source directory, but we strongly advise
advise building it in a separate build directory. For example, if you building it in a separate build directory. For example, if you have
have unpacked the glibc sources in `/src/gnu/glibc-2.3', create a unpacked the glibc sources in `/src/gnu/glibc-2.3', create a directory
directory `/src/gnu/glibc-build' to put the object files in. This `/src/gnu/glibc-build' to put the object files in. This allows
allows removing the whole build directory in case an error occurs, removing the whole build directory in case an error occurs, which is the
which is the safest way to get a fresh start and should always be done. safest way to get a fresh start and should always be done.
From your object directory, run the shell script `configure' located From your object directory, run the shell script `configure' located
at the top level of the source tree. In the scenario above, you'd type at the top level of the source tree. In the scenario above, you'd type
@ -214,16 +214,16 @@ library. You may need to set `AR' and `RANLIB' to cross-compiling
versions of `ar' and `ranlib' if the native tools are not configured to versions of `ar' and `ranlib' if the native tools are not configured to
work with object files for the target you configured for. work with object files for the target you configured for.
Installing the C Library A.2 Installing the C Library
======================== ============================
To install the library and its header files, and the Info files of To install the library and its header files, and the Info files of the
the manual, type `env LANGUAGE=C LC_ALL=C make install'. This will manual, type `env LANGUAGE=C LC_ALL=C make install'. This will build
build things, if necessary, before installing them; however, you should things, if necessary, before installing them; however, you should still
still compile everything first. If you are installing glibc as your compile everything first. If you are installing glibc as your primary
primary C library, we recommend that you shut the system down to C library, we recommend that you shut the system down to single-user
single-user mode first, and reboot afterward. This minimizes the risk mode first, and reboot afterward. This minimizes the risk of breaking
of breaking things when the library changes out from underneath. things when the library changes out from underneath.
If you're upgrading from Linux libc5 or some other C library, you If you're upgrading from Linux libc5 or some other C library, you
need to replace the `/usr/include' with a fresh directory before need to replace the `/usr/include' with a fresh directory before
@ -288,10 +288,10 @@ which is in `/usr/share/zoneinfo' to the file `/etc/localtime'. For
Germany, you might execute `ln -s /usr/share/zoneinfo/Europe/Berlin Germany, you might execute `ln -s /usr/share/zoneinfo/Europe/Berlin
/etc/localtime'. /etc/localtime'.
Recommended Tools for Compilation A.3 Recommended Tools for Compilation
================================= =====================================
We recommend installing the following GNU tools before attempting to We recommend installing the following GNU tools before attempting to
build the GNU C library: build the GNU C library:
* GNU `make' 3.79 or newer * GNU `make' 3.79 or newer
@ -362,10 +362,10 @@ and if you change any of the message translation files you will need
You may also need these packages if you upgrade your source tree using You may also need these packages if you upgrade your source tree using
patches, although we try to avoid this. patches, although we try to avoid this.
Supported Configurations A.4 Supported Configurations
======================== ============================
The GNU C Library currently supports configurations that match the The GNU C Library currently supports configurations that match the
following patterns: following patterns:
alpha*-*-linux alpha*-*-linux
@ -420,7 +420,9 @@ used to run on the following configurations:
they are not supported at the moment. They probably don't compile; they are not supported at the moment. They probably don't compile;
they definitely don't work anymore. Porting the library is not hard. they definitely don't work anymore. Porting the library is not hard.
If you are interested in doing a port, please contact the glibc If you are interested in doing a port, please contact the glibc
maintainers by sending electronic mail to <bug-glibc@gnu.org>. maintainers. Start at `http://www.gnu.org/software/libc/' and read the
references there on how to go about getting involved and contacting the
developers.
Valid cases of `iX86' include `i386', `i486', `i586', and `i686'. Valid cases of `iX86' include `i386', `i486', `i586', and `i686'.
All of those configurations produce a library that can run on this All of those configurations produce a library that can run on this
@ -432,17 +434,17 @@ some `i686' specific instructions. To generate code for other models,
you have to configure for that model and give GCC the appropriate you have to configure for that model and give GCC the appropriate
`-march=' and `-mcpu=' compiler switches via CFLAGS. `-march=' and `-mcpu=' compiler switches via CFLAGS.
Specific advice for GNU/Linux systems A.5 Specific advice for GNU/Linux systems
===================================== =========================================
If you are installing GNU libc on a GNU/Linux system, you need to If you are installing GNU libc on a GNU/Linux system, you need to have
have the header files from a 2.2 or newer kernel around for reference. the header files from a 2.2 or newer kernel around for reference. For
For some architectures, like ia64, sh and hppa, you need at least some architectures, like ia64, sh and hppa, you need at least headers
headers from kernel 2.3.99 (sh and hppa) or 2.4.0 (ia64). You do not from kernel 2.3.99 (sh and hppa) or 2.4.0 (ia64). You do not need to
need to use that kernel, just have its headers where glibc can access use that kernel, just have its headers where glibc can access at them.
at them. The easiest way to do this is to unpack it in a directory The easiest way to do this is to unpack it in a directory such as
such as `/usr/src/linux-2.2.1'. In that directory, run `make config' `/usr/src/linux-2.2.1'. In that directory, run `make config' and
and accept all the defaults. Then run `make include/linux/version.h'. accept all the defaults. Then run `make include/linux/version.h'.
Finally, configure glibc with the option Finally, configure glibc with the option
`--with-headers=/usr/src/linux-2.2.1/include'. Use the most recent `--with-headers=/usr/src/linux-2.2.1/include'. Use the most recent
kernel you can get your hands on. kernel you can get your hands on.
@ -480,17 +482,17 @@ installed there.
library on your system against the new library for the sake of new code, library on your system against the new library for the sake of new code,
but keep the old libraries around for old binaries to use. This is but keep the old libraries around for old binaries to use. This is
complicated and difficult. Consult the Glibc2 HOWTO at complicated and difficult. Consult the Glibc2 HOWTO at
<http://www.imaxx.net/~thrytis/glibc> for details. `http://www.imaxx.net/~thrytis/glibc' for details.
You cannot use `nscd' with 2.0 kernels, due to bugs in the You cannot use `nscd' with 2.0 kernels, due to bugs in the
kernel-side thread support. `nscd' happens to hit these bugs kernel-side thread support. `nscd' happens to hit these bugs
particularly hard, but you might have problems with any threaded particularly hard, but you might have problems with any threaded
program. program.
Reporting Bugs A.6 Reporting Bugs
============== ==================
There are probably bugs in the GNU C library. There are certainly There are probably bugs in the GNU C library. There are certainly
errors and omissions in this manual. If you report them, they will get errors and omissions in this manual. If you report them, they will get
fixed. If you don't, no one will ever know about them and they will fixed. If you don't, no one will ever know about them and they will
remain unfixed for all eternity, if not longer. remain unfixed for all eternity, if not longer.
@ -498,9 +500,9 @@ remain unfixed for all eternity, if not longer.
It is a good idea to verify that the problem has not already been It is a good idea to verify that the problem has not already been
reported. Bugs are documented in two places: The file `BUGS' describes reported. Bugs are documented in two places: The file `BUGS' describes
a number of well known bugs and the bug tracking system has a WWW a number of well known bugs and the bug tracking system has a WWW
interface at <http://www-gnats.gnu.org:8080/cgi-bin/wwwgnats.pl>. The interface at `http://sources.redhat.com/bugzilla/'. The WWW interface
WWW interface gives you access to open and closed reports. A closed gives you access to open and closed reports. A closed report normally
report normally includes a patch or a hint on solving the problem. includes a patch or a hint on solving the problem.
To report a bug, first you must find it. With any luck, this will To report a bug, first you must find it. With any luck, this will
be the hard part. Once you've found a bug, make sure it's really a be the hard part. Once you've found a bug, make sure it's really a
@ -521,21 +523,13 @@ library, you really only need to narrow it down to one library function
call, if possible. This should not be too difficult. call, if possible. This should not be too difficult.
The final step when you have a simple test case is to report the bug. The final step when you have a simple test case is to report the bug.
Do this using the `glibcbug' script. It is installed with libc, or if Do this using the WWW interface to the bug database.
you haven't installed it, will be in your build directory. Send your
test case, the results you got, the results you expected, and what you
think the problem might be (if you've thought of anything). `glibcbug'
will insert the configuration information we need to see, and ship the
report off to <bugs@gnu.org>. Don't send a message there directly; it
is fed to a program that expects mail to be formatted in a particular
way. Use the script.
If you are not sure how a function should behave, and this manual If you are not sure how a function should behave, and this manual
doesn't tell you, that's a bug in the manual. Report that too! If the doesn't tell you, that's a bug in the manual. Report that too! If the
function's behavior disagrees with the manual, then either the library function's behavior disagrees with the manual, then either the library
or the manual has a bug, so report the disagreement. If you find any or the manual has a bug, so report the disagreement. If you find any
errors or omissions in this manual, please report them to the Internet errors or omissions in this manual, please report them to the bug
address <bug-glibc-manual@gnu.org>. If you refer to specific sections database. If you refer to specific sections of the manual, please
of the manual, please include the section names for easier include the section names for easier identification.
identification.

4
locale/iso-3166.def
View File

@ -2,7 +2,9 @@
* Defines the country codes and abbreviations according to ISO 3166. * Defines the country codes and abbreviations according to ISO 3166.
* This is used in ld-address.c (address_finish). * This is used in ld-address.c (address_finish).
* *
* If you find something missing or wrong contact <bug-glibc@gnu.org> * If you find something missing or wrong, please go to the URL
* http://www.gnu.org/software/libc/bugs.html and follow
* instructions there to file a bug report.
*/ */
DEFINE_COUNTRY_CODE ("AFGHANISTAN", AF, AFG, 4) DEFINE_COUNTRY_CODE ("AFGHANISTAN", AF, AFG, 4)
DEFINE_COUNTRY_CODE ("ALBANIA", AL, ALB, 8) DEFINE_COUNTRY_CODE ("ALBANIA", AL, ALB, 8)

4
locale/iso-4217.def
View File

@ -2,7 +2,9 @@
* Defines the valid international currency symbols according to ISO 4217. * Defines the valid international currency symbols according to ISO 4217.
* This is used in monetary.c(monetary_check). * This is used in monetary.c(monetary_check).
* *
* If you find something missing or wrong contact <bug-glibc@gnu.org> * If you find something missing or wrong, please go to the URL
* http://www.gnu.org/software/libc/bugs.html and follow
* instructions there to file a bug report.
* *
* !!! The list has to be sorted !!! * !!! The list has to be sorted !!!
*/ */

4
locale/iso-639.def
View File

@ -3,7 +3,9 @@
* This is used in ld-address.c (address_finish). * This is used in ld-address.c (address_finish).
* *
* Format is: ("English name", 639-1-code, 639-2/T-code, 639-2/B-code) * Format is: ("English name", 639-1-code, 639-2/T-code, 639-2/B-code)
* If you find something missing or wrong contact <bug-glibc@gnu.org> * If you find something missing or wrong, please go to the URL
* http://www.gnu.org/software/libc/bugs.html and follow
* instructions there to file a bug report.
*/ */
DEFINE_LANGUAGE_CODE ("Abkhazian", ab, abk, abk) DEFINE_LANGUAGE_CODE ("Abkhazian", ab, abk, abk)

4
manual/install.texi
View File

@ -474,7 +474,9 @@ Since no one has volunteered to test and fix these configurations,
they are not supported at the moment. They probably don't compile; they are not supported at the moment. They probably don't compile;
they definitely don't work anymore. Porting the library is not hard. they definitely don't work anymore. Porting the library is not hard.
If you are interested in doing a port, please contact the glibc If you are interested in doing a port, please contact the glibc
maintainers by sending electronic mail to @email{bug-glibc@@gnu.org}. maintainers. Start at @url{http://www.gnu.org/software/libc/} and
read the references there on how to go about getting involved and
contacting the developers.
Valid cases of @samp{i@var{x}86} include @samp{i386}, @samp{i486}, Valid cases of @samp{i@var{x}86} include @samp{i386}, @samp{i486},
@samp{i586}, and @samp{i686}. All of those configurations produce a @samp{i586}, and @samp{i686}. All of those configurations produce a

1
posix/cpio.h
View File

@ -2,7 +2,6 @@
This file is part of the GNU C Library. This file is part of the GNU C Library.
Copyright (C) 1992, 1998 Free Software Foundation, Inc. Copyright (C) 1992, 1998 Free Software Foundation, Inc.
NOTE: The canonical source of this file is maintained with the GNU cpio. NOTE: The canonical source of this file is maintained with the GNU cpio.
Bugs can be reported to bug-glibc@gnu.org.
The GNU C Library is free software; you can redistribute it and/or The GNU C Library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public modify it under the terms of the GNU Lesser General Public