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