]>
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 | 11 | Before you do anything else, you should read the FAQ at |
a306c790 | 12 | @url{https://sourceware.org/glibc/wiki/FAQ}. It answers common |
7ac30cc5 AJ |
13 | questions and describes problems you may experience with compilation |
14 | and installation. | |
3c20b9b6 | 15 | |
00c1176b | 16 | You will need recent versions of several GNU tools: definitely GCC and |
fe959e1e | 17 | GNU Make, and possibly others. @xref{Tools for Compilation}, below. |
00c1176b | 18 | |
ee0a148a | 19 | @ifclear plain |
00c1176b UD |
20 | @menu |
21 | * Configuring and compiling:: How to compile and test GNU libc. | |
a4d62195 UD |
22 | * Running make install:: How to install it once you've got it |
23 | compiled. | |
00c1176b | 24 | * Tools for Compilation:: You'll need these first. |
90d1d40b | 25 | * Linux:: Specific advice for GNU/Linux systems. |
00c1176b UD |
26 | * Reporting Bugs:: So they'll get fixed. |
27 | @end menu | |
ee0a148a | 28 | @end ifclear |
00c1176b UD |
29 | |
30 | @node Configuring and compiling | |
1f77f049 | 31 | @appendixsec Configuring and compiling @theglibc{} |
1792d4db UD |
32 | @cindex configuring |
33 | @cindex compiling | |
00c1176b | 34 | |
1f77f049 | 35 | @Theglibc{} cannot be compiled in the source directory. You must build |
3858bf28 | 36 | it in a separate build directory. For example, if you have unpacked |
1f77f049 JM |
37 | the @glibcadj{} sources in @file{/src/gnu/glibc-@var{version}}, |
38 | create a directory | |
e8b1163e | 39 | @file{/src/gnu/glibc-build} to put the object files in. This allows |
3858bf28 RM |
40 | removing the whole build directory in case an error occurs, which is |
41 | the safest way to get a fresh start and should always be done. | |
00c1176b | 42 | |
a4d62195 | 43 | From your object directory, run the shell script @file{configure} located |
00c1176b UD |
44 | at the top level of the source tree. In the scenario above, you'd type |
45 | ||
46 | @smallexample | |
f1e86fca | 47 | $ ../glibc-@var{version}/configure @var{args@dots{}} |
00c1176b UD |
48 | @end smallexample |
49 | ||
3858bf28 | 50 | Please note that even though you're building in a separate build |
e6bdb741 AJ |
51 | directory, the compilation may need to create or modify files and |
52 | directories in the source directory. | |
f76d7052 | 53 | |
00c1176b | 54 | @noindent |
3858bf28 RM |
55 | @code{configure} takes many options, but the only one that is usually |
56 | mandatory is @samp{--prefix}. This option tells @code{configure} | |
1f77f049 | 57 | where you want @theglibc{} installed. This defaults to @file{/usr/local}, |
3858bf28 | 58 | but the normal setting to install as the standard system library is |
a7a93d50 JM |
59 | @samp{--prefix=/usr} for @gnulinuxsystems{} and @samp{--prefix=} (an |
60 | empty prefix) for @gnuhurdsystems{}. | |
00c1176b | 61 | |
db9881ec JM |
62 | It may also be useful to pass @samp{CC=@var{compiler}} and |
63 | @code{CFLAGS=@var{flags}} arguments to @code{configure}. @code{CC} | |
64 | selects the C compiler that will be used, and @code{CFLAGS} sets | |
65 | optimization options for the compiler. Any compiler options required | |
66 | for all compilations, such as options selecting an ABI or a processor | |
67 | for which to generate code, should be included in @code{CC}. Options | |
68 | that may be overridden by the @glibcadj{} build system for particular | |
69 | files, such as for optimization and debugging, should go in | |
70 | @code{CFLAGS}. The default value of @code{CFLAGS} is @samp{-g -O2}, | |
71 | and @theglibc{} cannot be compiled without optimization, so if | |
72 | @code{CFLAGS} is specified it must enable optimization. For example: | |
73 | ||
74 | @smallexample | |
75 | $ ../glibc-@var{version}/configure CC="gcc -m32" CFLAGS="-O3" | |
76 | @end smallexample | |
00c1176b | 77 | |
a4d62195 UD |
78 | The following list describes all of the available options for |
79 | @code{configure}: | |
3c20b9b6 UD |
80 | |
81 | @table @samp | |
00c1176b UD |
82 | @item --prefix=@var{directory} |
83 | Install machine-independent data files in subdirectories of | |
84 | @file{@var{directory}}. The default is to install in @file{/usr/local}. | |
85 | ||
86 | @item --exec-prefix=@var{directory} | |
87 | Install the library and other machine-dependent files in subdirectories | |
88 | of @file{@var{directory}}. The default is to the @samp{--prefix} | |
04b9968b | 89 | directory if that option is specified, or @file{/usr/local} otherwise. |
00c1176b UD |
90 | |
91 | @item --with-headers=@var{directory} | |
92 | Look for kernel header files in @var{directory}, not | |
1f77f049 JM |
93 | @file{/usr/include}. @Theglibc{} needs information from the kernel's header |
94 | files describing the interface to the kernel. @Theglibc{} will normally | |
abd923db | 95 | look in @file{/usr/include} for them, |
04b9968b | 96 | but if you specify this option, it will look in @var{DIRECTORY} instead. |
00c1176b UD |
97 | |
98 | This option is primarily of use on a system where the headers in | |
1f77f049 | 99 | @file{/usr/include} come from an older version of @theglibc{}. Conflicts can |
02c4bbad | 100 | occasionally happen in this case. You can also use this option if you want to |
1f77f049 | 101 | compile @theglibc{} with a newer set of kernel headers than the ones found in |
00c1176b UD |
102 | @file{/usr/include}. |
103 | ||
d2830ba4 | 104 | @item --enable-kernel=@var{version} |
a7a93d50 | 105 | This option is currently only useful on @gnulinuxsystems{}. The |
d2830ba4 UD |
106 | @var{version} parameter should have the form X.Y.Z and describes the |
107 | smallest version of the Linux kernel the generated library is expected | |
108 | to support. The higher the @var{version} number is, the less | |
109 | compatibility code is added, and the faster the code gets. | |
110 | ||
3c20b9b6 UD |
111 | @item --with-binutils=@var{directory} |
112 | Use the binutils (assembler and linker) in @file{@var{directory}}, not | |
a4d62195 | 113 | the ones the C compiler would default to. You can use this option if |
3c20b9b6 | 114 | the default binutils on your system cannot deal with all the constructs |
1f77f049 | 115 | in @theglibc{}. In that case, @code{configure} will detect the |
a4d62195 UD |
116 | problem and suppress these constructs, so that the library will still be |
117 | usable, but functionality may be lost---for example, you can't build a | |
118 | shared libc with old binutils. | |
3c20b9b6 | 119 | |
6413fcde FW |
120 | @item --with-nonshared-cflags=@var{cflags} |
121 | Use additional compiler flags @var{cflags} to build the parts of the | |
122 | library which are always statically linked into applications and | |
123 | libraries even with shared linking (that is, the object files contained | |
124 | in @file{lib*_nonshared.a} libraries). The build process will | |
125 | automatically use the appropriate flags, but this option can be used to | |
126 | set additional flags required for building applications and libraries, | |
127 | to match local policy. For example, if such a policy requires that all | |
128 | code linked into applications must be built with source fortification, | |
129 | @samp{--with-nonshared-cflags=-Wp,-D_FORTIFY_SOURCE=2} will make sure | |
130 | that the objects in @file{libc_nonshared.a} are compiled with this flag | |
131 | (although this will not affect the generated code in this particular | |
132 | case and potentially change debugging information and metadata only). | |
133 | ||
9ba202c7 FW |
134 | @item --with-rtld-early-cflags=@var{cflags} |
135 | Use additional compiler flags @var{cflags} to build the early startup | |
136 | code of the dynamic linker. These flags can be used to enable early | |
137 | dynamic linker diagnostics to run on CPUs which are not compatible with | |
138 | the rest of @theglibc{}, for example, due to compiler flags which target | |
139 | a later instruction set architecture (ISA). | |
140 | ||
bada2e31 L |
141 | @item --with-timeoutfactor=@var{NUM} |
142 | Specify an integer @var{NUM} to scale the timeout of test programs. | |
143 | This factor can be changed at run time using @env{TIMEOUTFACTOR} | |
144 | environment variable. | |
145 | ||
b5ca0fb0 UD |
146 | @c disable static doesn't work currently |
147 | @c @item --disable-static | |
fb06851d | 148 | @c Don't build static libraries. Static libraries aren't that useful these |
b5ca0fb0 | 149 | @c days, but we recommend you build them in case you need them. |
3c20b9b6 | 150 | |
00c1176b | 151 | @item --disable-shared |
a4d62195 UD |
152 | Don't build shared libraries even if it is possible. Not all systems |
153 | support shared libraries; you need ELF support and (currently) the GNU | |
154 | linker. | |
3c20b9b6 | 155 | |
23645707 SP |
156 | @item --disable-default-pie |
157 | Don't build glibc programs and the testsuite as position independent | |
158 | executables (PIE). By default, glibc programs and tests are created as | |
159 | position independent executables on targets that support it. If the toolchain | |
160 | and architecture support it, static executables are built as static PIE and the | |
161 | resulting glibc can be used with the GCC option, -static-pie, which is | |
162 | available with GCC 8 or above, to create static PIE. | |
9d7a3741 | 163 | |
e6c69509 | 164 | @item --enable-cet |
9e38f455 | 165 | @itemx --enable-cet=permissive |
e6c69509 | 166 | Enable Intel Control-flow Enforcement Technology (CET) support. When |
9e38f455 L |
167 | @theglibc{} is built with @option{--enable-cet} or |
168 | @option{--enable-cet=permissive}, the resulting library | |
e6c69509 L |
169 | is protected with indirect branch tracking (IBT) and shadow stack |
170 | (SHSTK)@. When CET is enabled, @theglibc{} is compatible with all | |
171 | existing executables and shared libraries. This feature is currently | |
172 | supported on i386, x86_64 and x32 with GCC 8 and binutils 2.29 or later. | |
173 | Note that when CET is enabled, @theglibc{} requires CPUs capable of | |
174 | multi-byte NOPs, like x86-64 processors as well as Intel Pentium Pro or | |
9e38f455 L |
175 | newer. With @option{--enable-cet}, it is an error to dlopen a non CET |
176 | enabled shared library in CET enabled application. With | |
177 | @option{--enable-cet=permissive}, CET is disabled when dlopening a | |
178 | non CET enabled shared library in CET enabled application. | |
e6c69509 | 179 | |
e84bd851 L |
180 | NOTE: @option{--enable-cet} has been tested for i686, x86_64 and x32 |
181 | on non-CET processors. @option{--enable-cet} has been tested for | |
9e38f455 | 182 | i686, x86_64 and x32 on CET processors. |
e84bd851 | 183 | |
33784089 RE |
184 | @item --enable-memory-tagging |
185 | Enable memory tagging support if the architecture supports it. When | |
186 | @theglibc{} is built with this option then the resulting library will | |
187 | be able to control the use of tagged memory when hardware support is | |
188 | present by use of the tunable @samp{glibc.mem.tagging}. This includes | |
189 | the generation of tagged memory when using the @code{malloc} APIs. | |
190 | ||
191 | At present only AArch64 platforms with MTE provide this functionality, | |
192 | although the library will still operate (without memory tagging) on | |
193 | older versions of the architecture. | |
194 | ||
195 | The default is to disable support for memory tagging. | |
196 | ||
00c1176b UD |
197 | @item --disable-profile |
198 | Don't build libraries with profiling information. You may want to use | |
199 | this option if you don't plan to do profiling. | |
f12944ec | 200 | |
00c1176b UD |
201 | @item --enable-static-nss |
202 | Compile static versions of the NSS (Name Service Switch) libraries. | |
203 | This is not recommended because it defeats the purpose of NSS; a program | |
204 | linked statically with the NSS libraries cannot be dynamically | |
205 | reconfigured to use a different name database. | |
206 | ||
740b3dbe L |
207 | @item --enable-hardcoded-path-in-tests |
208 | By default, dynamic tests are linked to run with the installed C library. | |
209 | This option hardcodes the newly built C library path in dynamic tests | |
210 | so that they can be invoked directly. | |
211 | ||
1cba4036 MF |
212 | @item --disable-timezone-tools |
213 | By default, timezone related utilities (@command{zic}, @command{zdump}, | |
44f826e3 | 214 | and @command{tzselect}) are installed with @theglibc{}. If you are building |
1cba4036 | 215 | these independently (e.g. by using the @samp{tzcode} package), then this |
44f826e3 | 216 | option will allow disabling the install of these. |
1cba4036 MF |
217 | |
218 | Note that you need to make sure the external tools are kept in sync with | |
219 | the versions that @theglibc{} expects as the data formats may change over | |
220 | time. Consult the @file{timezone} subdirectory for more details. | |
221 | ||
03baef1c NA |
222 | @item --enable-stack-protector |
223 | @itemx --enable-stack-protector=strong | |
224 | @itemx --enable-stack-protector=all | |
225 | Compile the C library and all other parts of the glibc package | |
226 | (including the threading and math libraries, NSS modules, and | |
227 | transliteration modules) using the GCC @option{-fstack-protector}, | |
228 | @option{-fstack-protector-strong} or @option{-fstack-protector-all} | |
229 | options to detect stack overruns. Only the dynamic linker and a small | |
230 | number of routines called directly from assembler are excluded from this | |
231 | protection. | |
232 | ||
2d6ab5df | 233 | @item --enable-bind-now |
94a4e9e4 FW |
234 | Disable lazy binding for installed shared objects and programs. This |
235 | provides additional security hardening because it enables full RELRO | |
236 | and a read-only global offset table (GOT), at the cost of slightly | |
237 | increased program load times. | |
2d6ab5df | 238 | |
e4608715 CD |
239 | @pindex pt_chown |
240 | @findex grantpt | |
241 | @item --enable-pt_chown | |
242 | The file @file{pt_chown} is a helper binary for @code{grantpt} | |
243 | (@pxref{Allocation, Pseudo-Terminals}) that is installed setuid root to | |
27fe5f2e FW |
244 | fix up pseudo-terminal ownership on GNU/Hurd. It is not required on |
245 | GNU/Linux, and @theglibc{} will not use the installed @file{pt_chown} | |
246 | program when configured with @option{--enable-pt_chown}. | |
e4608715 | 247 | |
a4ecc9eb JM |
248 | @item --disable-werror |
249 | By default, @theglibc{} is built with @option{-Werror}. If you wish | |
250 | to build without this option (for example, if building with a newer | |
251 | version of GCC than this version of @theglibc{} was tested with, so | |
252 | new warnings cause the build with @option{-Werror} to fail), you can | |
253 | configure with @option{--disable-werror}. | |
254 | ||
21933112 | 255 | @item --disable-mathvec |
b55a155f RJ |
256 | By default for x86_64, @theglibc{} is built with the vector math library. |
257 | Use this option to disable the vector math library. | |
21933112 | 258 | |
e69d994a ZW |
259 | @item --disable-crypt |
260 | Do not install the passphrase-hashing library @file{libcrypt} or the | |
261 | header file @file{crypt.h}. @file{unistd.h} will still declare the | |
262 | function @code{crypt}. Using this option does not change the set of | |
263 | programs that may need to be linked with @option{-lcrypt}; it only | |
264 | means that @theglibc{} will not provide that library. | |
265 | ||
266 | This option is for hackers and distributions experimenting with | |
267 | independently-maintained implementations of libcrypt. It may become | |
268 | the default in a future release. | |
269 | ||
ebae2f5a MC |
270 | @item --disable-scv |
271 | Disable using @code{scv} instruction for syscalls. All syscalls will use | |
272 | @code{sc} instead, even if the kernel supports @code{scv}. PowerPC only. | |
273 | ||
00c1176b UD |
274 | @item --build=@var{build-system} |
275 | @itemx --host=@var{host-system} | |
04b9968b | 276 | These options are for cross-compiling. If you specify both options and |
00c1176b | 277 | @var{build-system} is different from @var{host-system}, @code{configure} |
1f77f049 | 278 | will prepare to cross-compile @theglibc{} from @var{build-system} to be used |
00c1176b UD |
279 | on @var{host-system}. You'll probably need the @samp{--with-headers} |
280 | option too, and you may have to override @var{configure}'s selection of | |
281 | the compiler and/or binutils. | |
282 | ||
a4d62195 UD |
283 | If you only specify @samp{--host}, @code{configure} will prepare for a |
284 | native compile but use what you specify instead of guessing what your | |
cf822e3c | 285 | system is. This is most useful to change the CPU submodel. For example, |
e98cdb38 CD |
286 | if @code{configure} guesses your machine as @code{i686-pc-linux-gnu} but |
287 | you want to compile a library for 586es, give | |
288 | @samp{--host=i586-pc-linux-gnu} or just @samp{--host=i586-linux} and add | |
289 | the appropriate compiler flags (@samp{-mcpu=i586} will do the trick) to | |
db9881ec | 290 | @code{CC}. |
1792d4db | 291 | |
a4d62195 | 292 | If you specify just @samp{--build}, @code{configure} will get confused. |
8b748aed JM |
293 | |
294 | @item --with-pkgversion=@var{version} | |
295 | Specify a description, possibly including a build number or build | |
296 | date, of the binaries being built, to be included in | |
297 | @option{--version} output from programs installed with @theglibc{}. | |
298 | For example, @option{--with-pkgversion='FooBar GNU/Linux glibc build | |
299 | 123'}. The default value is @samp{GNU libc}. | |
300 | ||
301 | @item --with-bugurl=@var{url} | |
302 | Specify the URL that users should visit if they wish to report a bug, | |
303 | to be included in @option{--help} output from programs installed with | |
304 | @theglibc{}. The default value refers to the main bug-reporting | |
305 | information for @theglibc{}. | |
3c20b9b6 UD |
306 | @end table |
307 | ||
00c1176b UD |
308 | To build the library and related programs, type @code{make}. This will |
309 | produce a lot of output, some of which may look like errors from | |
b55a155f | 310 | @code{make} but aren't. Look for error messages from @code{make} |
a4d62195 | 311 | containing @samp{***}. Those indicate that something is seriously wrong. |
00c1176b | 312 | |
3858bf28 RM |
313 | The compilation process can take a long time, depending on the |
314 | configuration and the speed of your machine. Some complex modules may | |
315 | take a very long time to compile, as much as several minutes on slower | |
316 | machines. Do not panic if the compiler appears to hang. | |
3c20b9b6 | 317 | |
8eadd4f3 UD |
318 | If you want to run a parallel make, simply pass the @samp{-j} option |
319 | with an appropriate numeric parameter to @code{make}. You need a recent | |
320 | GNU @code{make} version, though. | |
f12944ec | 321 | |
04b9968b UD |
322 | To build and run test programs which exercise some of the library |
323 | facilities, type @code{make check}. If it does not complete | |
324 | successfully, do not use the built library, and report a bug after | |
325 | verifying that the problem is not already known. @xref{Reporting Bugs}, | |
326 | for instructions on reporting bugs. Note that some of the tests assume | |
327 | they are not being run by @code{root}. We recommend you compile and | |
1f77f049 | 328 | test @theglibc{} as an unprivileged user. |
3c20b9b6 | 329 | |
8eadd4f3 | 330 | Before reporting bugs make sure there is no problem with your system. |
a4d62195 | 331 | The tests (and later installation) use some pre-existing files of the |
8eadd4f3 UD |
332 | system such as @file{/etc/passwd}, @file{/etc/nsswitch.conf} and others. |
333 | These files must all contain correct and sensible content. | |
334 | ||
d6fe5e58 JM |
335 | Normally, @code{make check} will run all the tests before reporting |
336 | all problems found and exiting with error status if any problems | |
337 | occurred. You can specify @samp{stop-on-test-failure=y} when running | |
338 | @code{make check} to make the test run stop and exit with an error | |
339 | status immediately when a failure occurs. | |
340 | ||
3c20b9b6 | 341 | To format the @cite{GNU C Library Reference Manual} for printing, type |
6a4888ff AJ |
342 | @w{@code{make dvi}}. You need a working @TeX{} installation to do |
343 | this. The distribution builds the on-line formatted version of the | |
344 | manual, as Info files, as part of the build process. You can build | |
345 | them manually with @w{@code{make info}}. | |
1792d4db | 346 | |
2e8048e5 UD |
347 | The library has a number of special-purpose configuration parameters |
348 | which you can find in @file{Makeconfig}. These can be overwritten with | |
349 | the file @file{configparms}. To change them, create a | |
350 | @file{configparms} in your build directory and add values as appropriate | |
351 | for your system. The file is included and parsed by @code{make} and has | |
352 | to follow the conventions for makefiles. | |
353 | ||
1f77f049 | 354 | It is easy to configure @theglibc{} for cross-compilation by |
2e8048e5 UD |
355 | setting a few variables in @file{configparms}. Set @code{CC} to the |
356 | cross-compiler for the target you configured the library for; it is | |
357 | important to use this same @code{CC} value when running | |
db9881ec JM |
358 | @code{configure}, like this: @samp{configure @var{target} |
359 | CC=@var{target}-gcc}. Set @code{BUILD_CC} to the compiler to use for programs | |
a4d62195 | 360 | run on the build system as part of compiling the library. You may need to |
e9433893 UD |
361 | set @code{AR} to cross-compiling versions of @code{ar} |
362 | if the native tools are not configured to work with | |
df381762 JM |
363 | object files for the target you configured for. When cross-compiling |
364 | @theglibc{}, it may be tested using @samp{make check | |
365 | test-wrapper="@var{srcdir}/scripts/cross-test-ssh.sh @var{hostname}"}, | |
366 | where @var{srcdir} is the absolute directory name for the main source | |
367 | directory and @var{hostname} is the host name of a system that can run | |
368 | the newly built binaries of @theglibc{}. The source and build | |
369 | directories must be visible at the same locations on both the build | |
370 | system and @var{hostname}. | |
496e36f2 LM |
371 | The @samp{cross-test-ssh.sh} script requires @samp{flock} from |
372 | @samp{util-linux} to work when @var{glibc_test_allow_time_setting} | |
373 | environment variable is set. | |
374 | ||
375 | It is also possible to execute tests, which require setting the date on | |
376 | the target machine. Following use cases are supported: | |
377 | @itemize @bullet | |
378 | @item | |
379 | @code{GLIBC_TEST_ALLOW_TIME_SETTING} is set in the environment in | |
380 | which eligible tests are executed and have the privilege to run | |
381 | @code{clock_settime}. In this case, nothing prevents those tests from | |
382 | running in parallel, so the caller shall assure that those tests | |
383 | are serialized or provide a proper wrapper script for them. | |
384 | ||
385 | @item | |
386 | The @code{cross-test-ssh.sh} script is used and one passes the | |
387 | @option{--allow-time-setting} flag. In this case, both sets | |
388 | @code{GLIBC_TEST_ALLOW_TIME_SETTING} and serialization of test | |
389 | execution are assured automatically. | |
390 | @end itemize | |
2e8048e5 | 391 | |
0eb69512 JM |
392 | In general, when testing @theglibc{}, @samp{test-wrapper} may be set |
393 | to the name and arguments of any program to run newly built binaries. | |
394 | This program must preserve the arguments to the binary being run, its | |
8540f6d2 | 395 | working directory and the standard input, output and error file |
4acc27ed RM |
396 | descriptors. If @samp{@var{test-wrapper} env} will not work to run a |
397 | program with environment variables set, then @samp{test-wrapper-env} | |
398 | must be set to a program that runs a newly built program with | |
399 | environment variable assignments in effect, those assignments being | |
400 | specified as @samp{@var{var}=@var{value}} before the name of the | |
401 | program to be run. If multiple assignments to the same variable are | |
402 | specified, the last assignment specified must take precedence. | |
403 | Similarly, if @samp{@var{test-wrapper} env -i} will not work to run a | |
404 | program with an environment completely empty of variables except those | |
405 | directly assigned, then @samp{test-wrapper-env-only} must be set; its | |
406 | use has the same syntax as @samp{test-wrapper-env}, the only | |
407 | difference in its semantics being starting with an empty set of | |
408 | environment variables rather than the ambient set. | |
0eb69512 | 409 | |
38560563 NT |
410 | For AArch64 with SVE, when testing @theglibc{}, @samp{test-wrapper} |
411 | may be set to "@var{srcdir}/sysdeps/unix/sysv/linux/aarch64/vltest.py | |
412 | @var{vector-length}" to change Vector Length. | |
2e8048e5 | 413 | |
085320f5 | 414 | @node Running make install |
1792d4db UD |
415 | @appendixsec Installing the C Library |
416 | @cindex installing | |
3c20b9b6 UD |
417 | |
418 | To install the library and its header files, and the Info files of the | |
686554bf | 419 | manual, type @code{make install}. This will |
a4d62195 | 420 | build things, if necessary, before installing them; however, you should |
1f77f049 | 421 | still compile everything first. If you are installing @theglibc{} as your |
920e11e9 UD |
422 | primary C library, we recommend that you shut the system down to |
423 | single-user mode first, and reboot afterward. This minimizes the risk | |
424 | of breaking things when the library changes out from underneath. | |
1792d4db | 425 | |
02c4bbad | 426 | @samp{make install} will do the entire job of upgrading from a |
1f77f049 JM |
427 | previous installation of @theglibc{} version 2.x. There may sometimes |
428 | be headers | |
02c4bbad JM |
429 | left behind from the previous installation, but those are generally |
430 | harmless. If you want to avoid leaving headers behind you can do | |
431 | things in the following order. | |
c559a3ca UD |
432 | |
433 | You must first build the library (@samp{make}), optionally check it | |
434 | (@samp{make check}), switch the include directories and then install | |
435 | (@samp{make install}). The steps must be done in this order. Not moving | |
436 | the directory before install will result in an unusable mixture of header | |
437 | files from both libraries, but configuring, building, and checking the | |
438 | library requires the ability to compile and run programs against the old | |
02c4bbad JM |
439 | library. The new @file{/usr/include}, after switching the include |
440 | directories and before installing the library should contain the Linux | |
441 | headers, but nothing else. If you do this, you will need to restore | |
1f77f049 | 442 | any headers from libraries other than @theglibc{} yourself after installing the |
62075f0f | 443 | library. |
c559a3ca | 444 | |
a82a3db9 MS |
445 | You can install @theglibc{} somewhere other than where you configured |
446 | it to go by setting the @code{DESTDIR} GNU standard make variable on | |
447 | the command line for @samp{make install}. The value of this variable | |
448 | is prepended to all the paths for installation. This is useful when | |
449 | setting up a chroot environment or preparing a binary distribution. | |
450 | The directory should be specified with an absolute file name. Installing | |
451 | with the @code{prefix} and @code{exec_prefix} GNU standard make variables | |
452 | set is not supported. | |
1792d4db | 453 | |
1f77f049 | 454 | @Theglibc{} includes a daemon called @code{nscd}, which you |
1792d4db UD |
455 | may or may not want to run. @code{nscd} caches name service lookups; it |
456 | can dramatically improve performance with NIS+, and may help with DNS as | |
a0edd63e | 457 | well. |
1792d4db UD |
458 | |
459 | One auxiliary program, @file{/usr/libexec/pt_chown}, is installed setuid | |
cdfc721b AM |
460 | @code{root} if the @samp{--enable-pt_chown} configuration option is used. |
461 | This program is invoked by the @code{grantpt} function; it sets the | |
462 | permissions on a pseudoterminal so it can be used by the calling process. | |
463 | If you are using a Linux kernel with the @code{devpts} filesystem enabled | |
464 | and mounted at @file{/dev/pts}, you don't need this program. | |
3c20b9b6 | 465 | |
08a5ee14 CD |
466 | After installation you should configure the timezone and install locales |
467 | for your system. The time zone configuration ensures that your system | |
468 | time matches the time for your current timezone. The locales ensure that | |
469 | the display of information on your system matches the expectations of | |
470 | your language and geographic region. | |
471 | ||
472 | @Theglibc{} is able to use two kinds of localization information sources, the | |
473 | first is a locale database named @file{locale-archive} which is generally | |
474 | installed as @file{/usr/lib/locale/locale-archive}. The locale archive has the | |
475 | benefit of taking up less space and being very fast to load, but only if you | |
476 | plan to install sixty or more locales. If you plan to install one or two | |
477 | locales you can instead install individual locales into their self-named | |
478 | directories e.g.@: @file{/usr/lib/locale/en_US.utf8}. For example to install | |
479 | the German locale using the character set for UTF-8 with name @code{de_DE} into | |
480 | the locale archive issue the command @samp{localedef -i de_DE -f UTF-8 de_DE}, | |
481 | and to install just the one locale issue the command @samp{localedef | |
482 | --no-archive -i de_DE -f UTF-8 de_DE}. To configure all locales that are | |
483 | supported by @theglibc{}, you can issue from your build directory the command | |
484 | @samp{make localedata/install-locales} to install all locales into the locale | |
485 | archive or @samp{make localedata/install-locale-files} to install all locales | |
486 | as files in the default configured locale installation directory (derived from | |
487 | @samp{--prefix} or @code{--localedir}). To install into an alternative system | |
488 | root use @samp{DESTDIR} e.g.@: @samp{make localedata/install-locale-files | |
489 | DESTDIR=/opt/glibc}, but note that this does not change the configured prefix. | |
d01d6319 | 490 | |
a4d62195 UD |
491 | To configure the locally used timezone, set the @code{TZ} environment |
492 | variable. The script @code{tzselect} helps you to select the right value. | |
493 | As an example, for Germany, @code{tzselect} would tell you to use | |
494 | @samp{TZ='Europe/Berlin'}. For a system wide installation (the given | |
495 | paths are for an installation with @samp{--prefix=/usr}), link the | |
d01d6319 UD |
496 | timezone file which is in @file{/usr/share/zoneinfo} to the file |
497 | @file{/etc/localtime}. For Germany, you might execute @samp{ln -s | |
498 | /usr/share/zoneinfo/Europe/Berlin /etc/localtime}. | |
499 | ||
00c1176b UD |
500 | @node Tools for Compilation |
501 | @appendixsec Recommended Tools for Compilation | |
3c20b9b6 UD |
502 | @cindex installation tools |
503 | @cindex tools, for installing library | |
504 | ||
505 | We recommend installing the following GNU tools before attempting to | |
1f77f049 | 506 | build @theglibc{}: |
3c20b9b6 UD |
507 | |
508 | @itemize @bullet | |
509 | @item | |
f2873d2d | 510 | GNU @code{make} 4.0 or newer |
3c20b9b6 | 511 | |
51990242 | 512 | As of relase time, GNU @code{make} 4.4 is the newest verified to work |
f650932b CD |
513 | to build @theglibc{}. |
514 | ||
3c20b9b6 | 515 | @item |
4dcbbc3b | 516 | GCC 6.2 or newer |
0e7727f7 | 517 | |
4dcbbc3b | 518 | GCC 6.2 or higher is required. In general it is recommended to use |
4863355a JM |
519 | the newest version of the compiler that is known to work for building |
520 | @theglibc{}, as newer compilers usually produce better code. As of | |
51990242 | 521 | release time, GCC 13.0 is the newest compiler verified to work to build |
4863355a | 522 | @theglibc{}. |
91ea72b7 | 523 | |
50545f5a PM |
524 | For PowerPC 64-bits little-endian (powerpc64le), a GCC version with support |
525 | for @option{-mno-gnu-attribute}, @option{-mabi=ieeelongdouble}, and | |
5c7ccc29 PM |
526 | @option{-mabi=ibmlondouble} is required. Likewise, the compiler must also |
527 | support passing @option{-mlong-double-128} with the preceding options. As | |
528 | of release, this implies GCC 7.4 and newer (excepting GCC 7.5.0, see GCC | |
529 | PR94200). These additional features are required for building the GNU C | |
530 | Library with support for IEEE long double. | |
531 | ||
532 | @c powerpc64le performs an autoconf test to verify the compiler compiles with | |
533 | @c commands like "$CC -c foo.c -mabi=ibmlongdouble -mlong-double-128". | |
50545f5a | 534 | |
758caf37 VG |
535 | For ARC architecture builds, GCC 8.3 or higher is needed. |
536 | ||
844b4d8b SL |
537 | For s390x architecture builds, GCC 7.1 or higher is needed (See gcc Bug 98269). |
538 | ||
022dfdce SL |
539 | For multi-arch support it is recommended to use a GCC which has been built with |
540 | support for GNU indirect functions. This ensures that correct debugging | |
541 | information is generated for functions selected by IFUNC resolvers. This | |
542 | support can either be enabled by configuring GCC with | |
543 | @samp{--enable-gnu-indirect-function}, or by enabling it by default by setting | |
544 | @samp{default_gnu_indirect_function} variable for a particular architecture in | |
545 | the GCC source file @file{gcc/config.gcc}. | |
546 | ||
1f77f049 JM |
547 | You can use whatever compiler you like to compile programs that use |
548 | @theglibc{}. | |
3c20b9b6 | 549 | |
90d1d40b | 550 | Check the FAQ for any special compiler issues on particular platforms. |
5713a71e | 551 | |
3c20b9b6 | 552 | @item |
073e8fa7 | 553 | GNU @code{binutils} 2.25 or later |
00c1176b | 554 | |
1f77f049 | 555 | You must use GNU @code{binutils} (as and ld) to build @theglibc{}. |
0c02c85f | 556 | No other assembler or linker has the necessary functionality at the |
51990242 | 557 | moment. As of release time, GNU @code{binutils} 2.39 is the newest |
04cb913d | 558 | verified to work to build @theglibc{}. |
3c20b9b6 | 559 | |
3a0acbdc PM |
560 | For PowerPC 64-bits little-endian (powerpc64le), @command{objcopy} is required |
561 | to support @option{--update-section}. This option requires binutils 2.26 or | |
562 | newer. | |
563 | ||
758caf37 VG |
564 | ARC architecture needs @code{binutils} 2.32 or higher for TLS related fixes. |
565 | ||
3c20b9b6 | 566 | @item |
3a12c70f | 567 | GNU @code{texinfo} 4.7 or later |
3c20b9b6 UD |
568 | |
569 | To correctly translate and install the Texinfo documentation you need | |
570 | this version of the @code{texinfo} package. Earlier versions do not | |
571 | understand all the tags used in the document, and the installation | |
1792d4db | 572 | mechanism for the info files is not present or works differently. |
51990242 | 573 | As of release time, @code{texinfo} 7.0.2 is the newest verified to work |
04cb913d | 574 | to build @theglibc{}. |
3c20b9b6 UD |
575 | |
576 | @item | |
12086fb4 | 577 | GNU @code{awk} 3.1.2, or higher |
00c1176b | 578 | |
12086fb4 RM |
579 | @code{awk} is used in several places to generate files. |
580 | Some @code{gawk} extensions are used, including the @code{asorti} | |
581 | function, which was introduced in version 3.1.2 of @code{gawk}. | |
6415fd2d | 582 | As of release time, @code{gawk} version 5.1.1 is the newest verified |
2c8f75f7 | 583 | to work to build @theglibc{}. |
00c1176b | 584 | |
1faaf703 JB |
585 | @item |
586 | GNU @code{bison} 2.7 or later | |
587 | ||
588 | @code{bison} is used to generate the @code{yacc} parser code in the @file{intl} | |
6415fd2d | 589 | subdirectory. As of release time, @code{bison} version 3.8.2 is the newest |
93493119 | 590 | verified to work to build @theglibc{}. |
1faaf703 | 591 | |
00c1176b UD |
592 | @item |
593 | Perl 5 | |
594 | ||
3c1622eb | 595 | Perl is not required, but if present it is used in some tests and the |
053c52b1 | 596 | @code{mtrace} program, to build the @glibcadj{} manual. As of release |
51990242 | 597 | time @code{perl} version 5.36.0 is the newest verified to work to |
053c52b1 | 598 | build @theglibc{}. |
3c20b9b6 | 599 | |
d66732e0 UD |
600 | @item |
601 | GNU @code{sed} 3.02 or newer | |
602 | ||
a4d62195 | 603 | @code{Sed} is used in several places to generate files. Most scripts work |
2c8f75f7 | 604 | with any version of @code{sed}. As of release time, @code{sed} version |
ad477489 | 605 | 4.8 is the newest verified to work to build @theglibc{}. |
d66732e0 | 606 | |
3c1622eb | 607 | @item |
c6982f7e | 608 | Python 3.4 or later |
3c1622eb | 609 | |
c6982f7e | 610 | Python is required to build @theglibc{}. As of release time, Python |
51990242 | 611 | 3.11 is the newest verified to work for building and testing |
c6982f7e | 612 | @theglibc{}. |
3c1622eb JM |
613 | |
614 | @item PExpect 4.0 | |
615 | ||
616 | The pretty printer tests drive GDB through test programs and compare | |
617 | its output to the printers'. PExpect is used to capture the output of | |
618 | GDB, and should be compatible with the Python version in your system. | |
6415fd2d | 619 | As of release time PExpect 4.8.0 is the newest verified to work to test |
3c1622eb JM |
620 | the pretty printers. |
621 | ||
622 | @item | |
623 | GDB 7.8 or later with support for Python 2.7/3.4 or later | |
624 | ||
625 | GDB itself needs to be configured with Python support in order to use | |
626 | the pretty printers. Notice that your system having Python available | |
627 | doesn't imply that GDB supports it, nor that your system's Python and | |
628 | GDB's have the same version. As of release time GNU @code{debugger} | |
7a52dfab | 629 | 12.1 is the newest verified to work to test the pretty printers. |
3c1622eb JM |
630 | |
631 | Unless Python, PExpect and GDB with Python support are present, the | |
632 | printer tests will report themselves as @code{UNSUPPORTED}. Notice | |
633 | that some of the printer tests require @theglibc{} to be compiled with | |
634 | debugging symbols. | |
3c20b9b6 UD |
635 | @end itemize |
636 | ||
637 | @noindent | |
cb8a6dbd | 638 | If you change any of the @file{configure.ac} files you will also need |
3c20b9b6 UD |
639 | |
640 | @itemize @bullet | |
641 | @item | |
f3f5d895 | 642 | GNU @code{autoconf} 2.69 (exactly) |
3c20b9b6 UD |
643 | @end itemize |
644 | ||
645 | @noindent | |
646 | and if you change any of the message translation files you will need | |
647 | ||
648 | @itemize @bullet | |
649 | @item | |
c26b4f64 | 650 | GNU @code{gettext} 0.10.36 or later |
f650932b | 651 | |
51990242 | 652 | As of release time, GNU @code{gettext} version 0.21.1 is the newest |
f650932b | 653 | version verified to work to build @theglibc{}. |
3c20b9b6 UD |
654 | @end itemize |
655 | ||
cc8623f1 | 656 | |
3c20b9b6 UD |
657 | @noindent |
658 | You may also need these packages if you upgrade your source tree using | |
659 | patches, although we try to avoid this. | |
660 | ||
1792d4db | 661 | @node Linux |
a7a93d50 | 662 | @appendixsec Specific advice for @gnulinuxsystems{} |
1792d4db UD |
663 | @cindex kernel header files |
664 | ||
a7a93d50 | 665 | If you are installing @theglibc{} on @gnulinuxsystems{}, you need to have |
5b4ecd3f | 666 | the header files from a 3.2 or newer kernel around for reference. |
e9203023 FW |
667 | (For the ia64 architecture, you need version 3.2.18 or newer because this |
668 | is the first version with support for the @code{accept4} system call.) | |
abd923db JM |
669 | These headers must be installed using @samp{make headers_install}; the |
670 | headers present in the kernel source directory are not suitable for | |
1f77f049 JM |
671 | direct use by @theglibc{}. You do not need to use that kernel, just have |
672 | its headers installed where @theglibc{} can access them, referred to here as | |
abd923db JM |
673 | @var{install-directory}. The easiest way to do this is to unpack it |
674 | in a directory such as @file{/usr/src/linux-@var{version}}. In that | |
675 | directory, run @samp{make headers_install | |
1f77f049 | 676 | INSTALL_HDR_PATH=@var{install-directory}}. Finally, configure @theglibc{} |
abd923db JM |
677 | with the option @samp{--with-headers=@var{install-directory}/include}. |
678 | Use the most recent kernel you can get your hands on. (If you are | |
1f77f049 | 679 | cross-compiling @theglibc{}, you need to specify |
abd923db JM |
680 | @samp{ARCH=@var{architecture}} in the @samp{make headers_install} |
681 | command, where @var{architecture} is the architecture name used by the | |
682 | Linux kernel, such as @samp{x86} or @samp{powerpc}.) | |
a8d87c92 | 683 | |
1f77f049 | 684 | After installing @theglibc{}, you may need to remove or rename |
abd923db JM |
685 | directories such as @file{/usr/include/linux} and |
686 | @file{/usr/include/asm}, and replace them with copies of directories | |
687 | such as @file{linux} and @file{asm} from | |
688 | @file{@var{install-directory}/include}. All directories present in | |
689 | @file{@var{install-directory}/include} should be copied, except that | |
1f77f049 | 690 | @theglibc{} provides its own version of @file{/usr/include/scsi}; the |
abd923db | 691 | files provided by the kernel should be copied without replacing those |
1f77f049 | 692 | provided by @theglibc{}. The @file{linux}, @file{asm} and |
abd923db | 693 | @file{asm-generic} directories are required to compile programs using |
1f77f049 | 694 | @theglibc{}; the other directories describe interfaces to the kernel but |
abd923db JM |
695 | are not required if not compiling programs using those interfaces. |
696 | You do not need to copy kernel headers if you did not specify an | |
697 | alternate kernel header source using @samp{--with-headers}. | |
1792d4db | 698 | |
a7a93d50 JM |
699 | The Filesystem Hierarchy Standard for @gnulinuxsystems{} expects some |
700 | components of the @glibcadj{} installation to be in | |
1792d4db | 701 | @file{/lib} and some in @file{/usr/lib}. This is handled automatically |
1f77f049 | 702 | if you configure @theglibc{} with @samp{--prefix=/usr}. If you set some other |
1792d4db UD |
703 | prefix or allow it to default to @file{/usr/local}, then all the |
704 | components are installed there. | |
705 | ||
51990242 | 706 | As of release time, Linux version 6.1.5 is the newest stable version verified |
6415fd2d CD |
707 | to work to build @theglibc{}. |
708 | ||
3c20b9b6 UD |
709 | @node Reporting Bugs |
710 | @appendixsec Reporting Bugs | |
711 | @cindex reporting bugs | |
712 | @cindex bugs, reporting | |
713 | ||
1f77f049 | 714 | There are probably bugs in @theglibc{}. There are certainly |
3c20b9b6 UD |
715 | errors and omissions in this manual. If you report them, they will get |
716 | fixed. If you don't, no one will ever know about them and they will | |
717 | remain unfixed for all eternity, if not longer. | |
718 | ||
04b9968b UD |
719 | It is a good idea to verify that the problem has not already been |
720 | reported. Bugs are documented in two places: The file @file{BUGS} | |
8b748aed JM |
721 | describes a number of well known bugs and the central @glibcadj{} |
722 | bug tracking system has a | |
612fdf25 | 723 | WWW interface at |
a306c790 | 724 | @url{https://sourceware.org/bugzilla/}. The WWW |
a4d62195 UD |
725 | interface gives you access to open and closed reports. A closed report |
726 | normally includes a patch or a hint on solving the problem. | |
612fdf25 | 727 | |
a4d62195 | 728 | To report a bug, first you must find it. With any luck, this will be the |
3c20b9b6 | 729 | hard part. Once you've found a bug, make sure it's really a bug. A |
1f77f049 | 730 | good way to do this is to see if @theglibc{} behaves the same way |
3c20b9b6 UD |
731 | some other C library does. If so, probably you are wrong and the |
732 | libraries are right (but not necessarily). If not, one of the libraries | |
1f77f049 | 733 | is probably wrong. It might not be @theglibc{}. Many historical |
1792d4db UD |
734 | Unix C libraries permit things that we don't, such as closing a file |
735 | twice. | |
736 | ||
1f77f049 | 737 | If you think you have found some way in which @theglibc{} does not |
1792d4db UD |
738 | conform to the ISO and POSIX standards (@pxref{Standards and |
739 | Portability}), that is definitely a bug. Report it! | |
3c20b9b6 UD |
740 | |
741 | Once you're sure you've found a bug, try to narrow it down to the | |
742 | smallest test case that reproduces the problem. In the case of a C | |
743 | library, you really only need to narrow it down to one library | |
744 | function call, if possible. This should not be too difficult. | |
745 | ||
746 | The final step when you have a simple test case is to report the bug. | |
8b748aed | 747 | Do this at @value{REPORT_BUGS_TO}. |
3c20b9b6 UD |
748 | |
749 | If you are not sure how a function should behave, and this manual | |
750 | doesn't tell you, that's a bug in the manual. Report that too! If the | |
751 | function's behavior disagrees with the manual, then either the library | |
752 | or the manual has a bug, so report the disagreement. If you find any | |
d40eb37a UD |
753 | errors or omissions in this manual, please report them to the |
754 | bug database. If you refer to specific | |
04b9968b UD |
755 | sections of the manual, please include the section names for easier |
756 | identification. |