]>
Commit | Line | Data |
---|---|---|
3c20b9b6 UD |
1 | @c This is for making the `INSTALL' file for the distribution. |
2 | @c Makeinfo ignores it when processing the file from the include. | |
3 | @setfilename INSTALL | |
1f77f049 | 4 | @include macros.texi |
3c20b9b6 UD |
5 | |
6 | @node Installation, Maintenance, Library Summary, Top | |
1f77f049 JM |
7 | @c %MENU% How to install the GNU C Library |
8 | @appendix Installing @theglibc{} | |
3c20b9b6 | 9 | |
a4d62195 | 10 | Before you do anything else, you should read the file @file{FAQ} located |
3c20b9b6 UD |
11 | at the top level of the source tree. This file answers common questions |
12 | and describes problems you may experience with compilation and | |
13 | installation. It is updated more frequently than this manual. | |
14 | ||
1f77f049 | 15 | Features can be added to @theglibc{} via @dfn{add-on} bundles. These are |
a4d62195 | 16 | separate tar files, which you unpack into the top level of the source |
1792d4db | 17 | tree. Then you give @code{configure} the @samp{--enable-add-ons} option |
b3af1a24 | 18 | to activate them, and they will be compiled into the library. |
00c1176b UD |
19 | |
20 | You will need recent versions of several GNU tools: definitely GCC and | |
fe959e1e | 21 | GNU Make, and possibly others. @xref{Tools for Compilation}, below. |
00c1176b UD |
22 | |
23 | @menu | |
24 | * Configuring and compiling:: How to compile and test GNU libc. | |
a4d62195 UD |
25 | * Running make install:: How to install it once you've got it |
26 | compiled. | |
00c1176b | 27 | * Tools for Compilation:: You'll need these first. |
90d1d40b | 28 | * Linux:: Specific advice for GNU/Linux systems. |
00c1176b UD |
29 | * Reporting Bugs:: So they'll get fixed. |
30 | @end menu | |
31 | ||
32 | @node Configuring and compiling | |
1f77f049 | 33 | @appendixsec Configuring and compiling @theglibc{} |
1792d4db UD |
34 | @cindex configuring |
35 | @cindex compiling | |
00c1176b | 36 | |
1f77f049 | 37 | @Theglibc{} cannot be compiled in the source directory. You must build |
3858bf28 | 38 | it in a separate build directory. For example, if you have unpacked |
1f77f049 JM |
39 | the @glibcadj{} sources in @file{/src/gnu/glibc-@var{version}}, |
40 | create a directory | |
e8b1163e | 41 | @file{/src/gnu/glibc-build} to put the object files in. This allows |
3858bf28 RM |
42 | removing the whole build directory in case an error occurs, which is |
43 | the safest way to get a fresh start and should always be done. | |
00c1176b | 44 | |
a4d62195 | 45 | From your object directory, run the shell script @file{configure} located |
00c1176b UD |
46 | at the top level of the source tree. In the scenario above, you'd type |
47 | ||
48 | @smallexample | |
f1e86fca | 49 | $ ../glibc-@var{version}/configure @var{args@dots{}} |
00c1176b UD |
50 | @end smallexample |
51 | ||
3858bf28 RM |
52 | Please note that even though you're building in a separate build |
53 | directory, the compilation needs to modify a few files in the source | |
f76d7052 UD |
54 | directory, especially some files in the manual subdirectory. |
55 | ||
00c1176b | 56 | @noindent |
3858bf28 RM |
57 | @code{configure} takes many options, but the only one that is usually |
58 | mandatory is @samp{--prefix}. This option tells @code{configure} | |
1f77f049 | 59 | where you want @theglibc{} installed. This defaults to @file{/usr/local}, |
3858bf28 RM |
60 | but the normal setting to install as the standard system library is |
61 | @samp{--prefix=/usr} for GNU/Linux systems and @samp{--prefix=} (an | |
62 | empty prefix) for GNU/Hurd systems. | |
00c1176b UD |
63 | |
64 | It may also be useful to set the @var{CC} and @var{CFLAGS} variables in | |
65 | the environment when running @code{configure}. @var{CC} selects the C | |
66 | compiler that will be used, and @var{CFLAGS} sets optimization options | |
67 | for the compiler. | |
68 | ||
a4d62195 UD |
69 | The following list describes all of the available options for |
70 | @code{configure}: | |
3c20b9b6 UD |
71 | |
72 | @table @samp | |
00c1176b UD |
73 | @item --prefix=@var{directory} |
74 | Install machine-independent data files in subdirectories of | |
75 | @file{@var{directory}}. The default is to install in @file{/usr/local}. | |
76 | ||
77 | @item --exec-prefix=@var{directory} | |
78 | Install the library and other machine-dependent files in subdirectories | |
79 | of @file{@var{directory}}. The default is to the @samp{--prefix} | |
04b9968b | 80 | directory if that option is specified, or @file{/usr/local} otherwise. |
00c1176b UD |
81 | |
82 | @item --with-headers=@var{directory} | |
83 | Look for kernel header files in @var{directory}, not | |
1f77f049 JM |
84 | @file{/usr/include}. @Theglibc{} needs information from the kernel's header |
85 | files describing the interface to the kernel. @Theglibc{} will normally | |
abd923db | 86 | look in @file{/usr/include} for them, |
04b9968b | 87 | but if you specify this option, it will look in @var{DIRECTORY} instead. |
00c1176b UD |
88 | |
89 | This option is primarily of use on a system where the headers in | |
1f77f049 | 90 | @file{/usr/include} come from an older version of @theglibc{}. Conflicts can |
02c4bbad | 91 | occasionally happen in this case. You can also use this option if you want to |
1f77f049 | 92 | compile @theglibc{} with a newer set of kernel headers than the ones found in |
00c1176b UD |
93 | @file{/usr/include}. |
94 | ||
95 | @item --enable-add-ons[=@var{list}] | |
3858bf28 RM |
96 | Specify add-on packages to include in the build. If this option is |
97 | specified with no list, it enables all the add-on packages it finds in | |
98 | the main source directory; this is the default behavior. You may | |
99 | specify an explicit list of add-ons to use in @var{list}, separated by | |
100 | spaces or commas (if you use spaces, remember to quote them from the | |
101 | shell). Each add-on in @var{list} can be an absolute directory name | |
102 | or can be a directory name relative to the main source directory, or | |
103 | relative to the build directory (that is, the current working directory). | |
f1e86fca | 104 | For example, @samp{--enable-add-ons=nptl,../glibc-libidn-@var{version}}. |
00c1176b | 105 | |
d2830ba4 | 106 | @item --enable-kernel=@var{version} |
90d1d40b | 107 | This option is currently only useful on GNU/Linux systems. The |
d2830ba4 UD |
108 | @var{version} parameter should have the form X.Y.Z and describes the |
109 | smallest version of the Linux kernel the generated library is expected | |
110 | to support. The higher the @var{version} number is, the less | |
111 | compatibility code is added, and the faster the code gets. | |
112 | ||
3c20b9b6 UD |
113 | @item --with-binutils=@var{directory} |
114 | Use the binutils (assembler and linker) in @file{@var{directory}}, not | |
a4d62195 | 115 | the ones the C compiler would default to. You can use this option if |
3c20b9b6 | 116 | the default binutils on your system cannot deal with all the constructs |
1f77f049 | 117 | in @theglibc{}. In that case, @code{configure} will detect the |
a4d62195 UD |
118 | problem and suppress these constructs, so that the library will still be |
119 | usable, but functionality may be lost---for example, you can't build a | |
120 | shared libc with old binutils. | |
3c20b9b6 | 121 | |
3c20b9b6 | 122 | @item --without-fp |
3c20b9b6 UD |
123 | Use this option if your computer lacks hardware floating-point support |
124 | and your operating system does not emulate an FPU. | |
125 | ||
b5ca0fb0 UD |
126 | @c disable static doesn't work currently |
127 | @c @item --disable-static | |
fb06851d | 128 | @c Don't build static libraries. Static libraries aren't that useful these |
b5ca0fb0 | 129 | @c days, but we recommend you build them in case you need them. |
3c20b9b6 | 130 | |
00c1176b | 131 | @item --disable-shared |
a4d62195 UD |
132 | Don't build shared libraries even if it is possible. Not all systems |
133 | support shared libraries; you need ELF support and (currently) the GNU | |
134 | linker. | |
3c20b9b6 | 135 | |
00c1176b UD |
136 | @item --disable-profile |
137 | Don't build libraries with profiling information. You may want to use | |
138 | this option if you don't plan to do profiling. | |
f12944ec | 139 | |
00c1176b UD |
140 | @item --disable-versioning |
141 | Don't compile the shared libraries with symbol version information. | |
04b9968b | 142 | Doing this will make the resulting library incompatible with old |
00c1176b UD |
143 | binaries, so it's not recommended. |
144 | ||
145 | @item --enable-static-nss | |
146 | Compile static versions of the NSS (Name Service Switch) libraries. | |
147 | This is not recommended because it defeats the purpose of NSS; a program | |
148 | linked statically with the NSS libraries cannot be dynamically | |
149 | reconfigured to use a different name database. | |
150 | ||
8d4b5a8a | 151 | @item --without-tls |
a4d62195 | 152 | By default the C library is built with support for thread-local storage |
8d4b5a8a UD |
153 | if the used tools support it. By using @samp{--without-tls} this can be |
154 | prevented though there generally is no reason since it creates | |
155 | compatibility problems. | |
156 | ||
00c1176b UD |
157 | @item --build=@var{build-system} |
158 | @itemx --host=@var{host-system} | |
04b9968b | 159 | These options are for cross-compiling. If you specify both options and |
00c1176b | 160 | @var{build-system} is different from @var{host-system}, @code{configure} |
1f77f049 | 161 | will prepare to cross-compile @theglibc{} from @var{build-system} to be used |
00c1176b UD |
162 | on @var{host-system}. You'll probably need the @samp{--with-headers} |
163 | option too, and you may have to override @var{configure}'s selection of | |
164 | the compiler and/or binutils. | |
165 | ||
a4d62195 UD |
166 | If you only specify @samp{--host}, @code{configure} will prepare for a |
167 | native compile but use what you specify instead of guessing what your | |
168 | system is. This is most useful to change the CPU submodel. For example, | |
169 | if @code{configure} guesses your machine as @code{i586-pc-linux-gnu} but | |
170 | you want to compile a library for 386es, give | |
171 | @samp{--host=i386-pc-linux-gnu} or just @samp{--host=i386-linux} and add | |
172 | the appropriate compiler flags (@samp{-mcpu=i386} will do the trick) to | |
173 | @var{CFLAGS}. | |
1792d4db | 174 | |
a4d62195 | 175 | If you specify just @samp{--build}, @code{configure} will get confused. |
3c20b9b6 UD |
176 | @end table |
177 | ||
00c1176b UD |
178 | To build the library and related programs, type @code{make}. This will |
179 | produce a lot of output, some of which may look like errors from | |
180 | @code{make} but isn't. Look for error messages from @code{make} | |
a4d62195 | 181 | containing @samp{***}. Those indicate that something is seriously wrong. |
00c1176b | 182 | |
3858bf28 RM |
183 | The compilation process can take a long time, depending on the |
184 | configuration and the speed of your machine. Some complex modules may | |
185 | take a very long time to compile, as much as several minutes on slower | |
186 | machines. Do not panic if the compiler appears to hang. | |
3c20b9b6 | 187 | |
8eadd4f3 UD |
188 | If you want to run a parallel make, simply pass the @samp{-j} option |
189 | with an appropriate numeric parameter to @code{make}. You need a recent | |
190 | GNU @code{make} version, though. | |
f12944ec | 191 | |
04b9968b UD |
192 | To build and run test programs which exercise some of the library |
193 | facilities, type @code{make check}. If it does not complete | |
194 | successfully, do not use the built library, and report a bug after | |
195 | verifying that the problem is not already known. @xref{Reporting Bugs}, | |
196 | for instructions on reporting bugs. Note that some of the tests assume | |
197 | they are not being run by @code{root}. We recommend you compile and | |
1f77f049 | 198 | test @theglibc{} as an unprivileged user. |
3c20b9b6 | 199 | |
8eadd4f3 | 200 | Before reporting bugs make sure there is no problem with your system. |
a4d62195 | 201 | The tests (and later installation) use some pre-existing files of the |
8eadd4f3 UD |
202 | system such as @file{/etc/passwd}, @file{/etc/nsswitch.conf} and others. |
203 | These files must all contain correct and sensible content. | |
204 | ||
3c20b9b6 UD |
205 | To format the @cite{GNU C Library Reference Manual} for printing, type |
206 | @w{@code{make dvi}}. You need a working @TeX{} installation to do this. | |
1792d4db UD |
207 | The distribution already includes the on-line formatted version of the |
208 | manual, as Info files. You can regenerate those with @w{@code{make | |
209 | info}}, but it shouldn't be necessary. | |
210 | ||
2e8048e5 UD |
211 | The library has a number of special-purpose configuration parameters |
212 | which you can find in @file{Makeconfig}. These can be overwritten with | |
213 | the file @file{configparms}. To change them, create a | |
214 | @file{configparms} in your build directory and add values as appropriate | |
215 | for your system. The file is included and parsed by @code{make} and has | |
216 | to follow the conventions for makefiles. | |
217 | ||
1f77f049 | 218 | It is easy to configure @theglibc{} for cross-compilation by |
2e8048e5 UD |
219 | setting a few variables in @file{configparms}. Set @code{CC} to the |
220 | cross-compiler for the target you configured the library for; it is | |
221 | important to use this same @code{CC} value when running | |
222 | @code{configure}, like this: @samp{CC=@var{target}-gcc configure | |
a4d62195 UD |
223 | @var{target}}. Set @code{BUILD_CC} to the compiler to use for programs |
224 | run on the build system as part of compiling the library. You may need to | |
e9433893 UD |
225 | set @code{AR} to cross-compiling versions of @code{ar} |
226 | if the native tools are not configured to work with | |
a4d62195 | 227 | object files for the target you configured for. |
2e8048e5 UD |
228 | |
229 | ||
085320f5 | 230 | @node Running make install |
1792d4db UD |
231 | @appendixsec Installing the C Library |
232 | @cindex installing | |
3c20b9b6 UD |
233 | |
234 | To install the library and its header files, and the Info files of the | |
920e11e9 | 235 | manual, type @code{env LANGUAGE=C LC_ALL=C make install}. This will |
a4d62195 | 236 | build things, if necessary, before installing them; however, you should |
1f77f049 | 237 | still compile everything first. If you are installing @theglibc{} as your |
920e11e9 UD |
238 | primary C library, we recommend that you shut the system down to |
239 | single-user mode first, and reboot afterward. This minimizes the risk | |
240 | of breaking things when the library changes out from underneath. | |
1792d4db | 241 | |
02c4bbad | 242 | @samp{make install} will do the entire job of upgrading from a |
1f77f049 JM |
243 | previous installation of @theglibc{} version 2.x. There may sometimes |
244 | be headers | |
02c4bbad JM |
245 | left behind from the previous installation, but those are generally |
246 | harmless. If you want to avoid leaving headers behind you can do | |
247 | things in the following order. | |
c559a3ca UD |
248 | |
249 | You must first build the library (@samp{make}), optionally check it | |
250 | (@samp{make check}), switch the include directories and then install | |
251 | (@samp{make install}). The steps must be done in this order. Not moving | |
252 | the directory before install will result in an unusable mixture of header | |
253 | files from both libraries, but configuring, building, and checking the | |
254 | library requires the ability to compile and run programs against the old | |
02c4bbad JM |
255 | library. The new @file{/usr/include}, after switching the include |
256 | directories and before installing the library should contain the Linux | |
257 | headers, but nothing else. If you do this, you will need to restore | |
1f77f049 | 258 | any headers from libraries other than @theglibc{} yourself after installing the |
62075f0f | 259 | library. |
c559a3ca | 260 | |
1f77f049 | 261 | You can install @theglibc{} somewhere other than where you configured it to go |
1792d4db UD |
262 | by setting the @code{install_root} variable on the command line for |
263 | @samp{make install}. The value of this variable is prepended to all the | |
264 | paths for installation. This is useful when setting up a chroot | |
bef24895 UD |
265 | environment or preparing a binary distribution. The directory should be |
266 | specified with an absolute file name. | |
1792d4db | 267 | |
1f77f049 | 268 | @Theglibc{} includes a daemon called @code{nscd}, which you |
1792d4db UD |
269 | may or may not want to run. @code{nscd} caches name service lookups; it |
270 | can dramatically improve performance with NIS+, and may help with DNS as | |
a0edd63e | 271 | well. |
1792d4db UD |
272 | |
273 | One auxiliary program, @file{/usr/libexec/pt_chown}, is installed setuid | |
274 | @code{root}. This program is invoked by the @code{grantpt} function; it | |
275 | sets the permissions on a pseudoterminal so it can be used by the | |
276 | calling process. This means programs like @code{xterm} and | |
277 | @code{screen} do not have to be setuid to get a pty. (There may be | |
440d13e2 UD |
278 | other reasons why they need privileges.) If you are using a 2.1 or |
279 | newer Linux kernel with the @code{devptsfs} or @code{devfs} filesystems | |
280 | providing pty slaves, you don't need this program; otherwise you do. | |
281 | The source for @file{pt_chown} is in @file{login/programs/pt_chown.c}. | |
3c20b9b6 | 282 | |
d01d6319 | 283 | After installation you might want to configure the timezone and locale |
1f77f049 | 284 | installation of your system. @Theglibc{} comes with a locale |
d01d6319 UD |
285 | database which gets configured with @code{localedef}. For example, to |
286 | set up a German locale with name @code{de_DE}, simply issue the command | |
8fc1e2ca | 287 | @samp{localedef -i de_DE -f ISO-8859-1 de_DE}. To configure all locales |
1f77f049 | 288 | that are supported by @theglibc{}, you can issue from your build directory the |
d01d6319 UD |
289 | command @samp{make localedata/install-locales}. |
290 | ||
a4d62195 UD |
291 | To configure the locally used timezone, set the @code{TZ} environment |
292 | variable. The script @code{tzselect} helps you to select the right value. | |
293 | As an example, for Germany, @code{tzselect} would tell you to use | |
294 | @samp{TZ='Europe/Berlin'}. For a system wide installation (the given | |
295 | paths are for an installation with @samp{--prefix=/usr}), link the | |
d01d6319 UD |
296 | timezone file which is in @file{/usr/share/zoneinfo} to the file |
297 | @file{/etc/localtime}. For Germany, you might execute @samp{ln -s | |
298 | /usr/share/zoneinfo/Europe/Berlin /etc/localtime}. | |
299 | ||
00c1176b UD |
300 | @node Tools for Compilation |
301 | @appendixsec Recommended Tools for Compilation | |
3c20b9b6 UD |
302 | @cindex installation tools |
303 | @cindex tools, for installing library | |
304 | ||
305 | We recommend installing the following GNU tools before attempting to | |
1f77f049 | 306 | build @theglibc{}: |
3c20b9b6 UD |
307 | |
308 | @itemize @bullet | |
309 | @item | |
2bbc70d5 | 310 | GNU @code{make} 3.79 or newer |
3c20b9b6 | 311 | |
1f77f049 JM |
312 | You need the latest version of GNU @code{make}. Modifying @theglibc{} |
313 | to work with other @code{make} programs would be so difficult that | |
a4d62195 UD |
314 | we recommend you port GNU @code{make} instead. @strong{Really.} We |
315 | recommend GNU @code{make} version 3.79. All earlier versions have severe | |
316 | bugs or lack features. | |
3c20b9b6 UD |
317 | |
318 | @item | |
0e7727f7 JM |
319 | GCC 4.3 or newer, GCC 4.6 recommended |
320 | ||
321 | GCC 4.3 or higher is required; as of this writing, GCC 4.6 is the | |
1f77f049 | 322 | compiler we advise to use to build @theglibc{}. |
91ea72b7 | 323 | |
1f77f049 JM |
324 | You can use whatever compiler you like to compile programs that use |
325 | @theglibc{}. | |
3c20b9b6 | 326 | |
90d1d40b | 327 | Check the FAQ for any special compiler issues on particular platforms. |
5713a71e | 328 | |
3c20b9b6 | 329 | @item |
bec039bc | 330 | GNU @code{binutils} 2.20 or later |
00c1176b | 331 | |
1f77f049 | 332 | You must use GNU @code{binutils} (as and ld) to build @theglibc{}. |
0c02c85f | 333 | No other assembler or linker has the necessary functionality at the |
2231b60e | 334 | moment. |
3c20b9b6 UD |
335 | |
336 | @item | |
407dc7a0 | 337 | GNU @code{texinfo} 3.12f |
3c20b9b6 UD |
338 | |
339 | To correctly translate and install the Texinfo documentation you need | |
340 | this version of the @code{texinfo} package. Earlier versions do not | |
341 | understand all the tags used in the document, and the installation | |
1792d4db | 342 | mechanism for the info files is not present or works differently. |
3c20b9b6 UD |
343 | |
344 | @item | |
8522a053 | 345 | GNU @code{awk} 3.0, or higher |
00c1176b | 346 | |
8522a053 UD |
347 | @code{Awk} is used in several places to generate files. |
348 | @code{gawk} 3.0 is known to work. | |
00c1176b UD |
349 | |
350 | @item | |
351 | Perl 5 | |
352 | ||
353 | Perl is not required, but it is used if present to test the | |
354 | installation. We may decide to use it elsewhere in the future. | |
3c20b9b6 | 355 | |
d66732e0 UD |
356 | @item |
357 | GNU @code{sed} 3.02 or newer | |
358 | ||
a4d62195 UD |
359 | @code{Sed} is used in several places to generate files. Most scripts work |
360 | with any version of @code{sed}. The known exception is the script | |
d66732e0 | 361 | @code{po2test.sed} in the @code{intl} subdirectory which is used to |
a4d62195 UD |
362 | generate @code{msgs.h} for the test suite. This script works correctly |
363 | only with GNU @code{sed} 3.02. If you like to run the test suite, you | |
b8668434 | 364 | should definitely upgrade @code{sed}. |
d66732e0 | 365 | |
3c20b9b6 UD |
366 | @end itemize |
367 | ||
368 | @noindent | |
369 | If you change any of the @file{configure.in} files you will also need | |
370 | ||
371 | @itemize @bullet | |
372 | @item | |
d4198074 | 373 | GNU @code{autoconf} 2.53 or higher |
3c20b9b6 UD |
374 | @end itemize |
375 | ||
376 | @noindent | |
377 | and if you change any of the message translation files you will need | |
378 | ||
379 | @itemize @bullet | |
380 | @item | |
c26b4f64 | 381 | GNU @code{gettext} 0.10.36 or later |
3c20b9b6 UD |
382 | @end itemize |
383 | ||
384 | @noindent | |
385 | You may also need these packages if you upgrade your source tree using | |
386 | patches, although we try to avoid this. | |
387 | ||
1792d4db | 388 | @node Linux |
90d1d40b | 389 | @appendixsec Specific advice for GNU/Linux systems |
1792d4db UD |
390 | @cindex kernel header files |
391 | ||
1f77f049 | 392 | If you are installing @theglibc{} on a GNU/Linux system, you need to have |
abd923db JM |
393 | the header files from a 2.6.19.1 or newer kernel around for reference. |
394 | These headers must be installed using @samp{make headers_install}; the | |
395 | headers present in the kernel source directory are not suitable for | |
1f77f049 JM |
396 | direct use by @theglibc{}. You do not need to use that kernel, just have |
397 | its headers installed where @theglibc{} can access them, referred to here as | |
abd923db JM |
398 | @var{install-directory}. The easiest way to do this is to unpack it |
399 | in a directory such as @file{/usr/src/linux-@var{version}}. In that | |
400 | directory, run @samp{make headers_install | |
1f77f049 | 401 | INSTALL_HDR_PATH=@var{install-directory}}. Finally, configure @theglibc{} |
abd923db JM |
402 | with the option @samp{--with-headers=@var{install-directory}/include}. |
403 | Use the most recent kernel you can get your hands on. (If you are | |
1f77f049 | 404 | cross-compiling @theglibc{}, you need to specify |
abd923db JM |
405 | @samp{ARCH=@var{architecture}} in the @samp{make headers_install} |
406 | command, where @var{architecture} is the architecture name used by the | |
407 | Linux kernel, such as @samp{x86} or @samp{powerpc}.) | |
a8d87c92 | 408 | |
1f77f049 | 409 | After installing @theglibc{}, you may need to remove or rename |
abd923db JM |
410 | directories such as @file{/usr/include/linux} and |
411 | @file{/usr/include/asm}, and replace them with copies of directories | |
412 | such as @file{linux} and @file{asm} from | |
413 | @file{@var{install-directory}/include}. All directories present in | |
414 | @file{@var{install-directory}/include} should be copied, except that | |
1f77f049 | 415 | @theglibc{} provides its own version of @file{/usr/include/scsi}; the |
abd923db | 416 | files provided by the kernel should be copied without replacing those |
1f77f049 | 417 | provided by @theglibc{}. The @file{linux}, @file{asm} and |
abd923db | 418 | @file{asm-generic} directories are required to compile programs using |
1f77f049 | 419 | @theglibc{}; the other directories describe interfaces to the kernel but |
abd923db JM |
420 | are not required if not compiling programs using those interfaces. |
421 | You do not need to copy kernel headers if you did not specify an | |
422 | alternate kernel header source using @samp{--with-headers}. | |
1792d4db | 423 | |
1f77f049 | 424 | GNU/Linux expects some components of the @glibcadj{} installation to be in |
1792d4db | 425 | @file{/lib} and some in @file{/usr/lib}. This is handled automatically |
1f77f049 | 426 | if you configure @theglibc{} with @samp{--prefix=/usr}. If you set some other |
1792d4db UD |
427 | prefix or allow it to default to @file{/usr/local}, then all the |
428 | components are installed there. | |
429 | ||
1792d4db UD |
430 | You cannot use @code{nscd} with 2.0 kernels, due to bugs in the |
431 | kernel-side thread support. @code{nscd} happens to hit these bugs | |
432 | particularly hard, but you might have problems with any threaded | |
433 | program. | |
3c20b9b6 UD |
434 | |
435 | @node Reporting Bugs | |
436 | @appendixsec Reporting Bugs | |
437 | @cindex reporting bugs | |
438 | @cindex bugs, reporting | |
439 | ||
1f77f049 | 440 | There are probably bugs in @theglibc{}. There are certainly |
3c20b9b6 UD |
441 | errors and omissions in this manual. If you report them, they will get |
442 | fixed. If you don't, no one will ever know about them and they will | |
443 | remain unfixed for all eternity, if not longer. | |
444 | ||
04b9968b UD |
445 | It is a good idea to verify that the problem has not already been |
446 | reported. Bugs are documented in two places: The file @file{BUGS} | |
612fdf25 AS |
447 | describes a number of well known bugs and the bug tracking system has a |
448 | WWW interface at | |
d40eb37a | 449 | @url{http://sources.redhat.com/bugzilla/}. The WWW |
a4d62195 UD |
450 | interface gives you access to open and closed reports. A closed report |
451 | normally includes a patch or a hint on solving the problem. | |
612fdf25 | 452 | |
a4d62195 | 453 | To report a bug, first you must find it. With any luck, this will be the |
3c20b9b6 | 454 | hard part. Once you've found a bug, make sure it's really a bug. A |
1f77f049 | 455 | good way to do this is to see if @theglibc{} behaves the same way |
3c20b9b6 UD |
456 | some other C library does. If so, probably you are wrong and the |
457 | libraries are right (but not necessarily). If not, one of the libraries | |
1f77f049 | 458 | is probably wrong. It might not be @theglibc{}. Many historical |
1792d4db UD |
459 | Unix C libraries permit things that we don't, such as closing a file |
460 | twice. | |
461 | ||
1f77f049 | 462 | If you think you have found some way in which @theglibc{} does not |
1792d4db UD |
463 | conform to the ISO and POSIX standards (@pxref{Standards and |
464 | Portability}), that is definitely a bug. Report it! | |
3c20b9b6 UD |
465 | |
466 | Once you're sure you've found a bug, try to narrow it down to the | |
467 | smallest test case that reproduces the problem. In the case of a C | |
468 | library, you really only need to narrow it down to one library | |
469 | function call, if possible. This should not be too difficult. | |
470 | ||
471 | The final step when you have a simple test case is to report the bug. | |
d40eb37a | 472 | Do this using the WWW interface to the bug database. |
3c20b9b6 UD |
473 | |
474 | If you are not sure how a function should behave, and this manual | |
475 | doesn't tell you, that's a bug in the manual. Report that too! If the | |
476 | function's behavior disagrees with the manual, then either the library | |
477 | or the manual has a bug, so report the disagreement. If you find any | |
d40eb37a UD |
478 | errors or omissions in this manual, please report them to the |
479 | bug database. If you refer to specific | |
04b9968b UD |
480 | sections of the manual, please include the section names for easier |
481 | identification. |