2012-02-28 14:44:20 +00:00
|
|
|
@include macros.texi
|
2012-11-09 22:13:45 +00:00
|
|
|
@include pkgvers.texi
|
1998-03-17 17:27:52 +00:00
|
|
|
|
2013-12-05 04:04:58 +00:00
|
|
|
@ifclear plain
|
2013-09-28 03:10:59 +00:00
|
|
|
@node Installation, Maintenance, Library Summary, Top
|
2013-12-05 04:04:58 +00:00
|
|
|
@end ifclear
|
|
|
|
|
|
2012-02-28 14:44:20 +00:00
|
|
|
@c %MENU% How to install the GNU C Library
|
|
|
|
|
@appendix Installing @theglibc{}
|
1998-03-17 17:27:52 +00:00
|
|
|
|
2012-05-03 07:46:57 +00:00
|
|
|
Before you do anything else, you should read the FAQ at
|
2017-11-16 06:19:26 +00:00
|
|
|
@url{https://sourceware.org/glibc/wiki/FAQ}. It answers common
|
2012-05-03 07:46:57 +00:00
|
|
|
questions and describes problems you may experience with compilation
|
|
|
|
|
and installation.
|
1998-03-17 17:27:52 +00:00
|
|
|
|
1998-11-04 23:04:21 +00:00
|
|
|
You will need recent versions of several GNU tools: definitely GCC and
|
1998-11-05 13:03:24 +00:00
|
|
|
GNU Make, and possibly others. @xref{Tools for Compilation}, below.
|
1998-11-04 23:04:21 +00:00
|
|
|
|
2013-12-19 01:53:22 +00:00
|
|
|
@ifclear plain
|
1998-11-04 23:04:21 +00:00
|
|
|
@menu
|
|
|
|
|
* Configuring and compiling:: How to compile and test GNU libc.
|
2002-04-03 09:17:17 +00:00
|
|
|
* Running make install:: How to install it once you've got it
|
|
|
|
|
compiled.
|
1998-11-04 23:04:21 +00:00
|
|
|
* Tools for Compilation:: You'll need these first.
|
2002-08-22 00:13:04 +00:00
|
|
|
* Linux:: Specific advice for GNU/Linux systems.
|
1998-11-04 23:04:21 +00:00
|
|
|
* Reporting Bugs:: So they'll get fixed.
|
|
|
|
|
@end menu
|
2013-12-19 01:53:22 +00:00
|
|
|
@end ifclear
|
1998-11-04 23:04:21 +00:00
|
|
|
|
|
|
|
|
@node Configuring and compiling
|
2012-02-28 14:44:20 +00:00
|
|
|
@appendixsec Configuring and compiling @theglibc{}
|
1998-11-09 18:21:06 +00:00
|
|
|
@cindex configuring
|
|
|
|
|
@cindex compiling
|
1998-11-04 23:04:21 +00:00
|
|
|
|
2012-02-28 14:44:20 +00:00
|
|
|
@Theglibc{} cannot be compiled in the source directory. You must build
|
2006-03-06 10:59:43 +00:00
|
|
|
it in a separate build directory. For example, if you have unpacked
|
2012-02-28 14:44:20 +00:00
|
|
|
the @glibcadj{} sources in @file{/src/gnu/glibc-@var{version}},
|
|
|
|
|
create a directory
|
2000-03-10 08:41:39 +00:00
|
|
|
@file{/src/gnu/glibc-build} to put the object files in. This allows
|
2006-03-06 10:59:43 +00:00
|
|
|
removing the whole build directory in case an error occurs, which is
|
|
|
|
|
the safest way to get a fresh start and should always be done.
|
1998-11-04 23:04:21 +00:00
|
|
|
|
2002-04-03 09:17:17 +00:00
|
|
|
From your object directory, run the shell script @file{configure} located
|
1998-11-04 23:04:21 +00:00
|
|
|
at the top level of the source tree. In the scenario above, you'd type
|
|
|
|
|
|
|
|
|
|
@smallexample
|
2012-02-21 01:01:28 +00:00
|
|
|
$ ../glibc-@var{version}/configure @var{args@dots{}}
|
1998-11-04 23:04:21 +00:00
|
|
|
@end smallexample
|
|
|
|
|
|
2006-03-06 10:59:43 +00:00
|
|
|
Please note that even though you're building in a separate build
|
2012-05-18 18:30:51 +00:00
|
|
|
directory, the compilation may need to create or modify files and
|
|
|
|
|
directories in the source directory.
|
1999-04-26 14:02:38 +00:00
|
|
|
|
1998-11-04 23:04:21 +00:00
|
|
|
@noindent
|
2006-03-06 10:59:43 +00:00
|
|
|
@code{configure} takes many options, but the only one that is usually
|
|
|
|
|
mandatory is @samp{--prefix}. This option tells @code{configure}
|
2012-02-28 14:44:20 +00:00
|
|
|
where you want @theglibc{} installed. This defaults to @file{/usr/local},
|
2006-03-06 10:59:43 +00:00
|
|
|
but the normal setting to install as the standard system library is
|
2012-03-08 01:27:38 +00:00
|
|
|
@samp{--prefix=/usr} for @gnulinuxsystems{} and @samp{--prefix=} (an
|
|
|
|
|
empty prefix) for @gnuhurdsystems{}.
|
1998-11-04 23:04:21 +00:00
|
|
|
|
2018-02-15 23:48:47 +00:00
|
|
|
It may also be useful to pass @samp{CC=@var{compiler}} and
|
|
|
|
|
@code{CFLAGS=@var{flags}} arguments to @code{configure}. @code{CC}
|
|
|
|
|
selects the C compiler that will be used, and @code{CFLAGS} sets
|
|
|
|
|
optimization options for the compiler. Any compiler options required
|
|
|
|
|
for all compilations, such as options selecting an ABI or a processor
|
|
|
|
|
for which to generate code, should be included in @code{CC}. Options
|
|
|
|
|
that may be overridden by the @glibcadj{} build system for particular
|
|
|
|
|
files, such as for optimization and debugging, should go in
|
|
|
|
|
@code{CFLAGS}. The default value of @code{CFLAGS} is @samp{-g -O2},
|
|
|
|
|
and @theglibc{} cannot be compiled without optimization, so if
|
|
|
|
|
@code{CFLAGS} is specified it must enable optimization. For example:
|
|
|
|
|
|
|
|
|
|
@smallexample
|
|
|
|
|
$ ../glibc-@var{version}/configure CC="gcc -m32" CFLAGS="-O3"
|
|
|
|
|
@end smallexample
|
1998-11-04 23:04:21 +00:00
|
|
|
|
2002-04-03 09:17:17 +00:00
|
|
|
The following list describes all of the available options for
|
|
|
|
|
@code{configure}:
|
1998-03-17 17:27:52 +00:00
|
|
|
|
|
|
|
|
@table @samp
|
1998-11-04 23:04:21 +00:00
|
|
|
@item --prefix=@var{directory}
|
|
|
|
|
Install machine-independent data files in subdirectories of
|
|
|
|
|
@file{@var{directory}}. The default is to install in @file{/usr/local}.
|
|
|
|
|
|
|
|
|
|
@item --exec-prefix=@var{directory}
|
|
|
|
|
Install the library and other machine-dependent files in subdirectories
|
|
|
|
|
of @file{@var{directory}}. The default is to the @samp{--prefix}
|
1999-08-27 19:06:58 +00:00
|
|
|
directory if that option is specified, or @file{/usr/local} otherwise.
|
1998-11-04 23:04:21 +00:00
|
|
|
|
|
|
|
|
@item --with-headers=@var{directory}
|
|
|
|
|
Look for kernel header files in @var{directory}, not
|
2012-02-28 14:44:20 +00:00
|
|
|
@file{/usr/include}. @Theglibc{} needs information from the kernel's header
|
|
|
|
|
files describing the interface to the kernel. @Theglibc{} will normally
|
2012-02-27 20:52:30 +00:00
|
|
|
look in @file{/usr/include} for them,
|
1999-08-27 19:06:58 +00:00
|
|
|
but if you specify this option, it will look in @var{DIRECTORY} instead.
|
1998-11-04 23:04:21 +00:00
|
|
|
|
|
|
|
|
This option is primarily of use on a system where the headers in
|
2012-02-28 14:44:20 +00:00
|
|
|
@file{/usr/include} come from an older version of @theglibc{}. Conflicts can
|
2012-02-18 18:31:53 +00:00
|
|
|
occasionally happen in this case. You can also use this option if you want to
|
2012-02-28 14:44:20 +00:00
|
|
|
compile @theglibc{} with a newer set of kernel headers than the ones found in
|
1998-11-04 23:04:21 +00:00
|
|
|
@file{/usr/include}.
|
|
|
|
|
|
2000-11-04 03:29:28 +00:00
|
|
|
@item --enable-kernel=@var{version}
|
2012-03-08 01:27:38 +00:00
|
|
|
This option is currently only useful on @gnulinuxsystems{}. The
|
2000-11-04 03:29:28 +00:00
|
|
|
@var{version} parameter should have the form X.Y.Z and describes the
|
|
|
|
|
smallest version of the Linux kernel the generated library is expected
|
|
|
|
|
to support. The higher the @var{version} number is, the less
|
|
|
|
|
compatibility code is added, and the faster the code gets.
|
|
|
|
|
|
1998-03-17 17:27:52 +00:00
|
|
|
@item --with-binutils=@var{directory}
|
|
|
|
|
Use the binutils (assembler and linker) in @file{@var{directory}}, not
|
2002-04-03 09:17:17 +00:00
|
|
|
the ones the C compiler would default to. You can use this option if
|
1998-03-17 17:27:52 +00:00
|
|
|
the default binutils on your system cannot deal with all the constructs
|
2012-02-28 14:44:20 +00:00
|
|
|
in @theglibc{}. In that case, @code{configure} will detect the
|
2002-04-03 09:17:17 +00:00
|
|
|
problem and suppress these constructs, so that the library will still be
|
|
|
|
|
usable, but functionality may be lost---for example, you can't build a
|
|
|
|
|
shared libc with old binutils.
|
1998-03-17 17:27:52 +00:00
|
|
|
|
2018-08-17 09:44:39 +00:00
|
|
|
@item --with-nonshared-cflags=@var{cflags}
|
|
|
|
|
Use additional compiler flags @var{cflags} to build the parts of the
|
|
|
|
|
library which are always statically linked into applications and
|
|
|
|
|
libraries even with shared linking (that is, the object files contained
|
|
|
|
|
in @file{lib*_nonshared.a} libraries). The build process will
|
|
|
|
|
automatically use the appropriate flags, but this option can be used to
|
|
|
|
|
set additional flags required for building applications and libraries,
|
|
|
|
|
to match local policy. For example, if such a policy requires that all
|
|
|
|
|
code linked into applications must be built with source fortification,
|
|
|
|
|
@samp{--with-nonshared-cflags=-Wp,-D_FORTIFY_SOURCE=2} will make sure
|
|
|
|
|
that the objects in @file{libc_nonshared.a} are compiled with this flag
|
|
|
|
|
(although this will not affect the generated code in this particular
|
|
|
|
|
case and potentially change debugging information and metadata only).
|
|
|
|
|
|
2022-01-14 19:16:05 +00:00
|
|
|
@item --with-rtld-early-cflags=@var{cflags}
|
|
|
|
|
Use additional compiler flags @var{cflags} to build the early startup
|
|
|
|
|
code of the dynamic linker. These flags can be used to enable early
|
|
|
|
|
dynamic linker diagnostics to run on CPUs which are not compatible with
|
|
|
|
|
the rest of @theglibc{}, for example, due to compiler flags which target
|
|
|
|
|
a later instruction set architecture (ISA).
|
|
|
|
|
|
2021-12-04 19:25:53 +00:00
|
|
|
@item --with-timeoutfactor=@var{NUM}
|
|
|
|
|
Specify an integer @var{NUM} to scale the timeout of test programs.
|
|
|
|
|
This factor can be changed at run time using @env{TIMEOUTFACTOR}
|
|
|
|
|
environment variable.
|
|
|
|
|
|
1999-04-10 12:48:55 +00:00
|
|
|
@c disable static doesn't work currently
|
|
|
|
|
@c @item --disable-static
|
2012-02-21 02:19:14 +00:00
|
|
|
@c Don't build static libraries. Static libraries aren't that useful these
|
1999-04-10 12:48:55 +00:00
|
|
|
@c days, but we recommend you build them in case you need them.
|
1998-03-17 17:27:52 +00:00
|
|
|
|
1998-11-04 23:04:21 +00:00
|
|
|
@item --disable-shared
|
2002-04-03 09:17:17 +00:00
|
|
|
Don't build shared libraries even if it is possible. Not all systems
|
|
|
|
|
support shared libraries; you need ELF support and (currently) the GNU
|
|
|
|
|
linker.
|
1998-03-17 17:27:52 +00:00
|
|
|
|
2021-12-08 05:51:26 +00:00
|
|
|
@item --disable-default-pie
|
|
|
|
|
Don't build glibc programs and the testsuite as position independent
|
|
|
|
|
executables (PIE). By default, glibc programs and tests are created as
|
|
|
|
|
position independent executables on targets that support it. If the toolchain
|
|
|
|
|
and architecture support it, static executables are built as static PIE and the
|
|
|
|
|
resulting glibc can be used with the GCC option, -static-pie, which is
|
|
|
|
|
available with GCC 8 or above, to create static PIE.
|
Add --enable-static-pie configure option to build static PIE [BZ #19574]
Static PIE extends address space layout randomization to static
executables. It provides additional security hardening benefits at
the cost of some memory and performance.
Dynamic linker, ld.so, is a standalone program which can be loaded at
any address. This patch adds a configure option, --enable-static-pie,
to embed the part of ld.so in static executable to create static position
independent executable (static PIE). A static PIE is similar to static
executable, but can be loaded at any address without help from a dynamic
linker. When --enable-static-pie is used to configure glibc, libc.a is
built as PIE and all static executables, including tests, are built as
static PIE. The resulting libc.a can be used together with GCC 8 or
above to build static PIE with the compiler option, -static-pie. But
GCC 8 isn't required to build glibc with --enable-static-pie. Only GCC
with PIE support is needed. When an older GCC is used to build glibc
with --enable-static-pie, proper input files are passed to linker to
create static executables as static PIE, together with "-z text" to
prevent dynamic relocations in read-only segments, which are not allowed
in static PIE.
The following changes are made for static PIE:
1. Add a new function, _dl_relocate_static_pie, to:
a. Get the run-time load address.
b. Read the dynamic section.
c. Perform dynamic relocations.
Dynamic linker also performs these steps. But static PIE doesn't load
any shared objects.
2. Call _dl_relocate_static_pie at entrance of LIBC_START_MAIN in
libc.a. crt1.o, which is used to create dynamic and non-PIE static
executables, is updated to include a dummy _dl_relocate_static_pie.
rcrt1.o is added to create static PIE, which will link in the real
_dl_relocate_static_pie. grcrt1.o is also added to create static PIE
with -pg. GCC 8 has been updated to support rcrt1.o and grcrt1.o for
static PIE.
Static PIE can work on all architectures which support PIE, provided:
1. Target must support accessing of local functions without dynamic
relocations, which is needed in start.S to call __libc_start_main with
function addresses of __libc_csu_init, __libc_csu_fini and main. All
functions in static PIE are local functions. If PIE start.S can't reach
main () defined in a shared object, the code sequence:
pass address of local_main to __libc_start_main
...
local_main:
tail call to main via PLT
can be used.
2. start.S is updated to check PIC instead SHARED for PIC code path and
avoid dynamic relocation, when PIC is defined and SHARED isn't defined,
to support static PIE.
3. All assembly codes are updated check PIC instead SHARED for PIC code
path to avoid dynamic relocations in read-only sections.
4. All assembly codes are updated check SHARED instead PIC for static
symbol name.
5. elf_machine_load_address in dl-machine.h are updated to support static
PIE.
6. __brk works without TLS nor dynamic relocations in read-only section
so that it can be used by __libc_setup_tls to initializes TLS in static
PIE.
NB: When glibc is built with GCC defaulted to PIE, libc.a is compiled
with -fPIE, regardless if --enable-static-pie is used to configure glibc.
When glibc is configured with --enable-static-pie, libc.a is compiled
with -fPIE, regardless whether GCC defaults to PIE or not. The same
libc.a can be used to build both static executable and static PIE.
There is no need for separate PIE copy of libc.a.
On x86-64, the normal static sln:
text data bss dec hex filename
625425 8284 5456 639165 9c0bd elf/sln
the static PIE sln:
text data bss dec hex filename
657626 20636 5392 683654 a6e86 elf/sln
The code size is increased by 5% and the binary size is increased by 7%.
Linker requirements to build glibc with --enable-static-pie:
1. Linker supports --no-dynamic-linker to remove PT_INTERP segment from
static PIE.
2. Linker can create working static PIE. The x86-64 linker needs the
fix for
https://sourceware.org/bugzilla/show_bug.cgi?id=21782
The i386 linker needs to be able to convert "movl main@GOT(%ebx), %eax"
to "leal main@GOTOFF(%ebx), %eax" if main is defined locally.
Binutils 2.29 or above are OK for i686 and x86-64. But linker status for
other targets need to be verified.
3. Linker should resolve undefined weak symbols to 0 in static PIE:
https://sourceware.org/bugzilla/show_bug.cgi?id=22269
4. Many ELF backend linkers incorrectly check bfd_link_pic for TLS
relocations, which should check bfd_link_executable instead:
https://sourceware.org/bugzilla/show_bug.cgi?id=22263
Tested on aarch64, i686 and x86-64.
Using GCC 7 and binutils master branch, build-many-glibcs.py with
--enable-static-pie with all patches for static PIE applied have the
following build successes:
PASS: glibcs-aarch64_be-linux-gnu build
PASS: glibcs-aarch64-linux-gnu build
PASS: glibcs-armeb-linux-gnueabi-be8 build
PASS: glibcs-armeb-linux-gnueabi build
PASS: glibcs-armeb-linux-gnueabihf-be8 build
PASS: glibcs-armeb-linux-gnueabihf build
PASS: glibcs-arm-linux-gnueabi build
PASS: glibcs-arm-linux-gnueabihf build
PASS: glibcs-arm-linux-gnueabihf-v7a build
PASS: glibcs-arm-linux-gnueabihf-v7a-disable-multi-arch build
PASS: glibcs-m68k-linux-gnu build
PASS: glibcs-microblazeel-linux-gnu build
PASS: glibcs-microblaze-linux-gnu build
PASS: glibcs-mips64el-linux-gnu-n32 build
PASS: glibcs-mips64el-linux-gnu-n32-nan2008 build
PASS: glibcs-mips64el-linux-gnu-n32-nan2008-soft build
PASS: glibcs-mips64el-linux-gnu-n32-soft build
PASS: glibcs-mips64el-linux-gnu-n64 build
PASS: glibcs-mips64el-linux-gnu-n64-nan2008 build
PASS: glibcs-mips64el-linux-gnu-n64-nan2008-soft build
PASS: glibcs-mips64el-linux-gnu-n64-soft build
PASS: glibcs-mips64-linux-gnu-n32 build
PASS: glibcs-mips64-linux-gnu-n32-nan2008 build
PASS: glibcs-mips64-linux-gnu-n32-nan2008-soft build
PASS: glibcs-mips64-linux-gnu-n32-soft build
PASS: glibcs-mips64-linux-gnu-n64 build
PASS: glibcs-mips64-linux-gnu-n64-nan2008 build
PASS: glibcs-mips64-linux-gnu-n64-nan2008-soft build
PASS: glibcs-mips64-linux-gnu-n64-soft build
PASS: glibcs-mipsel-linux-gnu build
PASS: glibcs-mipsel-linux-gnu-nan2008 build
PASS: glibcs-mipsel-linux-gnu-nan2008-soft build
PASS: glibcs-mipsel-linux-gnu-soft build
PASS: glibcs-mips-linux-gnu build
PASS: glibcs-mips-linux-gnu-nan2008 build
PASS: glibcs-mips-linux-gnu-nan2008-soft build
PASS: glibcs-mips-linux-gnu-soft build
PASS: glibcs-nios2-linux-gnu build
PASS: glibcs-powerpc64le-linux-gnu build
PASS: glibcs-powerpc64-linux-gnu build
PASS: glibcs-tilegxbe-linux-gnu-32 build
PASS: glibcs-tilegxbe-linux-gnu build
PASS: glibcs-tilegx-linux-gnu-32 build
PASS: glibcs-tilegx-linux-gnu build
PASS: glibcs-tilepro-linux-gnu build
and the following build failures:
FAIL: glibcs-alpha-linux-gnu build
elf/sln is failed to link due to:
assertion fail bfd/elf64-alpha.c:4125
This is caused by linker bug and/or non-PIC code in PIE libc.a.
FAIL: glibcs-hppa-linux-gnu build
elf/sln is failed to link due to:
collect2: fatal error: ld terminated with signal 11 [Segmentation fault]
https://sourceware.org/bugzilla/show_bug.cgi?id=22537
FAIL: glibcs-ia64-linux-gnu build
elf/sln is failed to link due to:
collect2: fatal error: ld terminated with signal 11 [Segmentation fault]
FAIL: glibcs-powerpc-linux-gnu build
FAIL: glibcs-powerpc-linux-gnu-soft build
FAIL: glibcs-powerpc-linux-gnuspe build
FAIL: glibcs-powerpc-linux-gnuspe-e500v1 build
elf/sln is failed to link due to:
ld: read-only segment has dynamic relocations.
This is caused by linker bug and/or non-PIC code in PIE libc.a. See:
https://sourceware.org/bugzilla/show_bug.cgi?id=22264
FAIL: glibcs-powerpc-linux-gnu-power4 build
elf/sln is failed to link due to:
findlocale.c:96:(.text+0x22c): @local call to ifunc memchr
This is caused by linker bug and/or non-PIC code in PIE libc.a.
FAIL: glibcs-s390-linux-gnu build
elf/sln is failed to link due to:
collect2: fatal error: ld terminated with signal 11 [Segmentation fault], core dumped
assertion fail bfd/elflink.c:14299
This is caused by linker bug and/or non-PIC code in PIE libc.a.
FAIL: glibcs-sh3eb-linux-gnu build
FAIL: glibcs-sh3-linux-gnu build
FAIL: glibcs-sh4eb-linux-gnu build
FAIL: glibcs-sh4eb-linux-gnu-soft build
FAIL: glibcs-sh4-linux-gnu build
FAIL: glibcs-sh4-linux-gnu-soft build
elf/sln is failed to link due to:
ld: read-only segment has dynamic relocations.
This is caused by linker bug and/or non-PIC code in PIE libc.a. See:
https://sourceware.org/bugzilla/show_bug.cgi?id=22263
Also TLS code sequence in SH assembly syscalls in glibc doesn't match TLS
code sequence expected by ld:
https://sourceware.org/bugzilla/show_bug.cgi?id=22270
FAIL: glibcs-sparc64-linux-gnu build
FAIL: glibcs-sparcv9-linux-gnu build
FAIL: glibcs-tilegxbe-linux-gnu build
FAIL: glibcs-tilegxbe-linux-gnu-32 build
FAIL: glibcs-tilegx-linux-gnu build
FAIL: glibcs-tilegx-linux-gnu-32 build
FAIL: glibcs-tilepro-linux-gnu build
elf/sln is failed to link due to:
ld: read-only segment has dynamic relocations.
This is caused by linker bug and/or non-PIC code in PIE libc.a. See:
https://sourceware.org/bugzilla/show_bug.cgi?id=22263
[BZ #19574]
* INSTALL: Regenerated.
* Makeconfig (real-static-start-installed-name): New.
(pic-default): Updated for --enable-static-pie.
(pie-default): New for --enable-static-pie.
(default-pie-ldflag): Likewise.
(+link-static-before-libc): Replace $(DEFAULT-LDFLAGS-$(@F))
with $(if $($(@F)-no-pie),$(no-pie-ldflag),$(default-pie-ldflag)).
Replace $(static-start-installed-name) with
$(real-static-start-installed-name).
(+prectorT): Updated for --enable-static-pie.
(+postctorT): Likewise.
(CFLAGS-.o): Add $(pie-default).
(CFLAGS-.op): Likewise.
* NEWS: Mention --enable-static-pie.
* config.h.in (ENABLE_STATIC_PIE): New.
* configure.ac (--enable-static-pie): New configure option.
(have-no-dynamic-linker): New LIBC_CONFIG_VAR.
(have-static-pie): Likewise.
Enable static PIE if linker supports --no-dynamic-linker.
(ENABLE_STATIC_PIE): New AC_DEFINE.
(enable-static-pie): New LIBC_CONFIG_VAR.
* configure: Regenerated.
* csu/Makefile (omit-deps): Add r$(start-installed-name) and
gr$(start-installed-name) for --enable-static-pie.
(extra-objs): Likewise.
(install-lib): Likewise.
(extra-objs): Add static-reloc.o and static-reloc.os
($(objpfx)$(start-installed-name)): Also depend on
$(objpfx)static-reloc.o.
($(objpfx)r$(start-installed-name)): New.
($(objpfx)g$(start-installed-name)): Also depend on
$(objpfx)static-reloc.os.
($(objpfx)gr$(start-installed-name)): New.
* csu/libc-start.c (LIBC_START_MAIN): Call _dl_relocate_static_pie
in libc.a.
* csu/libc-tls.c (__libc_setup_tls): Add main_map->l_addr to
initimage.
* csu/static-reloc.c: New file.
* elf/Makefile (routines): Add dl-reloc-static-pie.
(elide-routines.os): Likewise.
(DEFAULT-LDFLAGS-tst-tls1-static-non-pie): Removed.
(tst-tls1-static-non-pie-no-pie): New.
* elf/dl-reloc-static-pie.c: New file.
* elf/dl-support.c (_dl_get_dl_main_map): New function.
* elf/dynamic-link.h (ELF_DURING_STARTUP): Also check
STATIC_PIE_BOOTSTRAP.
* elf/get-dynamic-info.h (elf_get_dynamic_info): Likewise.
* gmon/Makefile (tests): Add tst-gmon-static-pie.
(tests-static): Likewise.
(DEFAULT-LDFLAGS-tst-gmon-static): Removed.
(tst-gmon-static-no-pie): New.
(CFLAGS-tst-gmon-static-pie.c): Likewise.
(CRT-tst-gmon-static-pie): Likewise.
(tst-gmon-static-pie-ENV): Likewise.
(tests-special): Likewise.
($(objpfx)tst-gmon-static-pie.out): Likewise.
(clean-tst-gmon-static-pie-data): Likewise.
($(objpfx)tst-gmon-static-pie-gprof.out): Likewise.
* gmon/tst-gmon-static-pie.c: New file.
* manual/install.texi: Document --enable-static-pie.
* sysdeps/generic/ldsodefs.h (_dl_relocate_static_pie): New.
(_dl_get_dl_main_map): Likewise.
* sysdeps/i386/configure.ac: Check if linker supports static PIE.
* sysdeps/x86_64/configure.ac: Likewise.
* sysdeps/i386/configure: Regenerated.
* sysdeps/x86_64/configure: Likewise.
* sysdeps/mips/Makefile (ASFLAGS-.o): Add $(pie-default).
(ASFLAGS-.op): Likewise.
2017-12-16 00:59:33 +00:00
|
|
|
|
2018-07-18 16:52:40 +00:00
|
|
|
@item --enable-cet
|
2020-04-27 22:44:07 +00:00
|
|
|
@itemx --enable-cet=permissive
|
2018-07-18 16:52:40 +00:00
|
|
|
Enable Intel Control-flow Enforcement Technology (CET) support. When
|
2020-04-27 22:44:07 +00:00
|
|
|
@theglibc{} is built with @option{--enable-cet} or
|
|
|
|
|
@option{--enable-cet=permissive}, the resulting library
|
2018-07-18 16:52:40 +00:00
|
|
|
is protected with indirect branch tracking (IBT) and shadow stack
|
|
|
|
|
(SHSTK)@. When CET is enabled, @theglibc{} is compatible with all
|
|
|
|
|
existing executables and shared libraries. This feature is currently
|
2024-01-03 20:09:23 +00:00
|
|
|
supported on x86_64 and x32 with GCC 8 and binutils 2.29 or later.
|
|
|
|
|
With @option{--enable-cet}, it is an error to dlopen a non CET
|
2020-04-27 22:44:07 +00:00
|
|
|
enabled shared library in CET enabled application. With
|
|
|
|
|
@option{--enable-cet=permissive}, CET is disabled when dlopening a
|
|
|
|
|
non CET enabled shared library in CET enabled application.
|
2018-07-18 16:52:40 +00:00
|
|
|
|
2024-01-05 13:41:03 +00:00
|
|
|
NOTE: @option{--enable-cet} is only supported on x86_64 and x32.
|
2018-07-19 19:04:56 +00:00
|
|
|
|
2020-12-21 15:03:03 +00:00
|
|
|
@item --enable-memory-tagging
|
|
|
|
|
Enable memory tagging support if the architecture supports it. When
|
|
|
|
|
@theglibc{} is built with this option then the resulting library will
|
|
|
|
|
be able to control the use of tagged memory when hardware support is
|
|
|
|
|
present by use of the tunable @samp{glibc.mem.tagging}. This includes
|
|
|
|
|
the generation of tagged memory when using the @code{malloc} APIs.
|
|
|
|
|
|
|
|
|
|
At present only AArch64 platforms with MTE provide this functionality,
|
|
|
|
|
although the library will still operate (without memory tagging) on
|
|
|
|
|
older versions of the architecture.
|
|
|
|
|
|
|
|
|
|
The default is to disable support for memory tagging.
|
|
|
|
|
|
1998-11-04 23:04:21 +00:00
|
|
|
@item --disable-profile
|
|
|
|
|
Don't build libraries with profiling information. You may want to use
|
|
|
|
|
this option if you don't plan to do profiling.
|
1998-04-21 09:43:11 +00:00
|
|
|
|
1998-11-04 23:04:21 +00:00
|
|
|
@item --enable-static-nss
|
|
|
|
|
Compile static versions of the NSS (Name Service Switch) libraries.
|
|
|
|
|
This is not recommended because it defeats the purpose of NSS; a program
|
|
|
|
|
linked statically with the NSS libraries cannot be dynamically
|
|
|
|
|
reconfigured to use a different name database.
|
|
|
|
|
|
2013-01-11 15:14:18 +00:00
|
|
|
@item --enable-hardcoded-path-in-tests
|
|
|
|
|
By default, dynamic tests are linked to run with the installed C library.
|
|
|
|
|
This option hardcodes the newly built C library path in dynamic tests
|
|
|
|
|
so that they can be invoked directly.
|
|
|
|
|
|
2015-09-18 18:00:05 +00:00
|
|
|
@item --disable-timezone-tools
|
Modernize and fix doc’s “Date and Time” (BZ 31876)
POSIX.1-2024 (now official) specifies tm_gmtoff and tm_zone.
This is a good time to update the manual’s “Date and Time”
chapter so I went through it, fixed some outdated
stuff that had been in there for decades, and improved it to match
POSIX.1-2024 better and to clarify some implementation-defined
behavior. Glibc already conforms to POSIX.1-2024 in these matters, so
this is merely a documentation change.
* manual/examples/strftim.c: Use snprintf instead of now-deprecated
function asctime. Check for localtime failure. Simplify by using
puts instead of fputs. Prefer ‘buf, sizeof buf’ to less-obvious
‘buffer, SIZE’.
* manual/examples/timespec_subtract.c: Modernize to use struct
timespec not struct timeval, and rename from timeval_subtract.c.
All uses changed. Check for overflow. Do not check for negative
return value, which ought to be OK since negative time_t is OK.
Use GNU indenting style.
* manual/time.texi:
Document CLOCKS_PER_SEC, TIME_UTC, timespec_get, timespec_getres,
strftime_l.
Document the storage lifetime of tm_zone and of tzname.
Caution against use of tzname, timezone and daylight, saying that
these variables have unspecified values when TZ is geographic.
This is what glibc actually does (contrary to what the manual said
before this patch), and POSIX is planned to say the same thing
<https://austingroupbugs.net/view.php?id=1816>.
Also say that directly accessing the variables is not thread-safe.
Say that localtime_r and ctime_r don’t necessarily set time zone
state. Similarly, in the tzset documentation, say that it is called
by ctime, localtime, mktime, strftime, not that it is called by all
time conversion functions that depend on the time zone.
Say that tm_isdst is useful mostly just for mktime, and that
other uses should prefer tm_gmtoff and tm_zone instead.
Do not say that strftime ignores tm_gmtoff and tm_zone, because
it doesn’t do that.
Document what gmtime does to tm_gmtoff and tm_zone.
Say that the asctime, asctime_r, ctime, and ctime_r are now deprecated
and/or obsolescent, and that behavior is undefined if the year is <
1000 or > 9999. Document strftime before these now-obsolescent
functions, so that readers see the useful function first.
Coin the terms “geographical format” and “proleptic format” for the
two main formats of TZ settings, to simplify exposition. Use this
wording consistently.
Update top-level proleptic syntax to match POSIX.1-2024, which glibc
already implements. Document the angle-bracket quoted forms of time
zone abbreviations in proleptic TZ. Say that time zone abbreviations
can contain only ASCII alphanumerics, ‘+’, and ‘-’.
Document what happens if the proleptic form specifies a DST
abbreviation and offset but omits the rules. POSIX says this is
implementation-defined so we need to document it. Although this
documentation mentions ‘posixrules’ tersely, we need to rethink
‘posixrules’ since I think it stops working after 2038.
Clarify wording about TZ settings beginning with ‘;’.
Say that timegm is in ISO C (as of C23).
Say that POSIX.1-2024 removed gettimeofday.
Say that tm_gmtoff and tm_zone are extensions to ISO C, which is
clearer than saying they are invisible in a struct ISO C enviroment,
and gives us more wiggle room if we want to make them visible in
strict ISO C, something that ISO C allows.
Drop mention of old standards like POSIX.1c and POSIX.2-1992 in the
text when the history is so old that it’s no longer useful in a
general-purpose manual.
Define Coordinated Universal Time (UTC), time zone, time zone ruleset,
and POSIX Epoch, and use these phrases more consistently.
Improve TZ examples to show more variety, and to reflect current
practice and timestamps. Remove obsolete example about Argentina.
Add an example for Ireland.
Don’t rely on GCC extensions when explaining ctime_r.
Do not say that difftime produces the mathematically correct result,
since it might be inexact.
For clock_t don’t say “as in the example above” when there is no
such example, and don’t say that casting to double works “properly
and consistently no matter what”, as it suffers from rounding and
overflow.
Don’t say broken-down time is not useful for calculations; it’s
merely painful.
Say that UTC is not defined before 1960.
Rename Time Zone Functions to Time Zone State. All uses changed.
Update Internet RFC 822 → 5322, 1305 → 5905. Drop specific years of
ISO 8601 as they don’t matter.
Minor style changes: @code{"..."} → @t{"..."} to avoid overquoting in
info files, @code → @env for environment variables, Daylight Saving
Time → daylight saving time, white space → whitespace, prime meridian
→ Prime Meridian.
2024-06-08 16:48:25 +00:00
|
|
|
By default, time zone related utilities (@command{zic}, @command{zdump},
|
2015-10-19 18:12:03 +00:00
|
|
|
and @command{tzselect}) are installed with @theglibc{}. If you are building
|
2015-09-18 18:00:05 +00:00
|
|
|
these independently (e.g. by using the @samp{tzcode} package), then this
|
2015-10-19 18:12:03 +00:00
|
|
|
option will allow disabling the install of these.
|
2015-09-18 18:00:05 +00:00
|
|
|
|
|
|
|
|
Note that you need to make sure the external tools are kept in sync with
|
|
|
|
|
the versions that @theglibc{} expects as the data formats may change over
|
|
|
|
|
time. Consult the @file{timezone} subdirectory for more details.
|
|
|
|
|
|
2016-12-26 09:08:18 +00:00
|
|
|
@item --enable-stack-protector
|
|
|
|
|
@itemx --enable-stack-protector=strong
|
|
|
|
|
@itemx --enable-stack-protector=all
|
|
|
|
|
Compile the C library and all other parts of the glibc package
|
|
|
|
|
(including the threading and math libraries, NSS modules, and
|
|
|
|
|
transliteration modules) using the GCC @option{-fstack-protector},
|
|
|
|
|
@option{-fstack-protector-strong} or @option{-fstack-protector-all}
|
|
|
|
|
options to detect stack overruns. Only the dynamic linker and a small
|
|
|
|
|
number of routines called directly from assembler are excluded from this
|
|
|
|
|
protection.
|
|
|
|
|
|
2017-03-02 13:44:28 +00:00
|
|
|
@item --enable-bind-now
|
2019-04-25 08:41:43 +00:00
|
|
|
Disable lazy binding for installed shared objects and programs. This
|
|
|
|
|
provides additional security hardening because it enables full RELRO
|
|
|
|
|
and a read-only global offset table (GOT), at the cost of slightly
|
|
|
|
|
increased program load times.
|
2017-03-02 13:44:28 +00:00
|
|
|
|
2013-07-19 06:42:03 +00:00
|
|
|
@pindex pt_chown
|
|
|
|
|
@findex grantpt
|
|
|
|
|
@item --enable-pt_chown
|
|
|
|
|
The file @file{pt_chown} is a helper binary for @code{grantpt}
|
|
|
|
|
(@pxref{Allocation, Pseudo-Terminals}) that is installed setuid root to
|
2020-10-07 12:55:04 +00:00
|
|
|
fix up pseudo-terminal ownership on GNU/Hurd. It is not required on
|
|
|
|
|
GNU/Linux, and @theglibc{} will not use the installed @file{pt_chown}
|
|
|
|
|
program when configured with @option{--enable-pt_chown}.
|
2013-07-19 06:42:03 +00:00
|
|
|
|
Use -Werror by default, add --disable-werror.
As discussed starting at
<https://sourceware.org/ml/libc-alpha/2014-11/msg00323.html>, this
patch makes the glibc build use -Werror by default to avoid
accidentally adding new warnings to the build. The configure option
--disable-werror can be used to disable this.
-Wno-error=undef is temporarily used because the build isn't clean
regarding -Wundef warnings. The idea is that once the remaining
-Wundef warnings have been cleaned up (in at least one configuration),
-Wno-error=undef will be removed.
I get a clean build and test on x86_64 (GCC 4.9 branch) with this
patch. The expectation is that this may well break the build for some
other configurations, and people seeing such breakage should make
appropriate fixes to fix or suppress the warnings for their
configurations. In some cases that may involve using pragmas as the
right fix (I think that will be right for the -Wno-inline issue for
MIPS I referred to in
<https://sourceware.org/ml/libc-alpha/2012-11/msg00798.html>, for
example), in some cases -Wno-error in sysdeps makefiles (__restore_rt
in MIPS sigaction, for example), in some cases substantive fixes for
the warnings.
Note that if, with a view to listing all the warnings then fixing them
all, you just look for "warning:" in output from building and testing
with --disable-werror, you'll see lots of warnings from the linker
about functions such as tmpnam. Those warnings can be ignored - only
compiler warnings are relevant to -Werror, not linker warnings.
* configure.ac (--disable-werror): New configure option.
(enable_werror): New AC_SUBST.
* configure: Regenerated.
* config.make.in (enable-werror): New variable.
* Makeconfig [$(enable-werror) = yes] (+gccwarn): Add -Werror
-Wno-error=undef.
(+gccwarn-c): Do not use -Werror=implicit-function-declaration.
* manual/install.texi (Configuring and compiling): Document
--disable-werror.
* INSTALL: Regenerated.
* debug/Makefile (CFLAGS-tst-chk1.c): Add -Wno-error.
(CFLAGS-tst-chk2.c): Likewise.
(CFLAGS-tst-chk3.c): Likewise.
(CFLAGS-tst-chk4.cc): Likewise.
(CFLAGS-tst-chk5.cc): Likewise.
(CFLAGS-tst-chk6.cc): Likewise.
(CFLAGS-tst-lfschk1.c): Likewise.
(CFLAGS-tst-lfschk2.c): Likewise.
(CFLAGS-tst-lfschk3.c): Likewise.
(CFLAGS-tst-lfschk4.cc): Likewise.
(CFLAGS-tst-lfschk5.cc): Likewise.
(CFLAGS-tst-lfschk6.cc): Likewise.
2014-12-10 01:14:48 +00:00
|
|
|
@item --disable-werror
|
|
|
|
|
By default, @theglibc{} is built with @option{-Werror}. If you wish
|
|
|
|
|
to build without this option (for example, if building with a newer
|
|
|
|
|
version of GCC than this version of @theglibc{} was tested with, so
|
|
|
|
|
new warnings cause the build with @option{-Werror} to fail), you can
|
|
|
|
|
configure with @option{--disable-werror}.
|
|
|
|
|
|
2015-06-09 11:25:49 +00:00
|
|
|
@item --disable-mathvec
|
2016-10-06 06:58:45 +00:00
|
|
|
By default for x86_64, @theglibc{} is built with the vector math library.
|
|
|
|
|
Use this option to disable the vector math library.
|
2015-06-09 11:25:49 +00:00
|
|
|
|
2024-06-20 22:28:13 +00:00
|
|
|
@item --disable-static-c++-tests
|
|
|
|
|
By default, if the C++ toolchain lacks support for static linking,
|
|
|
|
|
configure fails to find the C++ header files and the glibc build fails.
|
|
|
|
|
@option{--disable-static-c++-link-check} allows the glibc build to finish,
|
|
|
|
|
but static C++ tests will fail if the C++ toolchain doesn't have the
|
|
|
|
|
necessary static C++ libraries. Use this option to skip the static C++
|
|
|
|
|
tests. This option implies @option{--disable-static-c++-link-check}.
|
|
|
|
|
|
2024-06-20 22:28:12 +00:00
|
|
|
@item --disable-static-c++-link-check
|
|
|
|
|
By default, if the C++ toolchain lacks support for static linking,
|
|
|
|
|
configure fails to find the C++ header files and the glibc build fails.
|
|
|
|
|
Use this option to disable the static C++ link check so that the C++
|
|
|
|
|
header files can be located. The newly built libc.a can be used to
|
|
|
|
|
create static C++ tests if the C++ toolchain has the necessary static
|
|
|
|
|
C++ libraries.
|
|
|
|
|
|
2021-04-09 17:47:27 +00:00
|
|
|
@item --disable-scv
|
|
|
|
|
Disable using @code{scv} instruction for syscalls. All syscalls will use
|
|
|
|
|
@code{sc} instead, even if the kernel supports @code{scv}. PowerPC only.
|
|
|
|
|
|
1998-11-04 23:04:21 +00:00
|
|
|
@item --build=@var{build-system}
|
|
|
|
|
@itemx --host=@var{host-system}
|
1999-08-27 19:06:58 +00:00
|
|
|
These options are for cross-compiling. If you specify both options and
|
1998-11-04 23:04:21 +00:00
|
|
|
@var{build-system} is different from @var{host-system}, @code{configure}
|
2012-02-28 14:44:20 +00:00
|
|
|
will prepare to cross-compile @theglibc{} from @var{build-system} to be used
|
1998-11-04 23:04:21 +00:00
|
|
|
on @var{host-system}. You'll probably need the @samp{--with-headers}
|
|
|
|
|
option too, and you may have to override @var{configure}'s selection of
|
|
|
|
|
the compiler and/or binutils.
|
|
|
|
|
|
2002-04-03 09:17:17 +00:00
|
|
|
If you only specify @samp{--host}, @code{configure} will prepare for a
|
|
|
|
|
native compile but use what you specify instead of guessing what your
|
2014-02-26 22:27:38 +00:00
|
|
|
system is. This is most useful to change the CPU submodel. For example,
|
2013-03-13 01:25:40 +00:00
|
|
|
if @code{configure} guesses your machine as @code{i686-pc-linux-gnu} but
|
|
|
|
|
you want to compile a library for 586es, give
|
|
|
|
|
@samp{--host=i586-pc-linux-gnu} or just @samp{--host=i586-linux} and add
|
|
|
|
|
the appropriate compiler flags (@samp{-mcpu=i586} will do the trick) to
|
2018-02-15 23:48:47 +00:00
|
|
|
@code{CC}.
|
1998-11-09 18:21:06 +00:00
|
|
|
|
2002-04-03 09:17:17 +00:00
|
|
|
If you specify just @samp{--build}, @code{configure} will get confused.
|
2012-11-09 22:13:45 +00:00
|
|
|
|
|
|
|
|
@item --with-pkgversion=@var{version}
|
|
|
|
|
Specify a description, possibly including a build number or build
|
|
|
|
|
date, of the binaries being built, to be included in
|
|
|
|
|
@option{--version} output from programs installed with @theglibc{}.
|
|
|
|
|
For example, @option{--with-pkgversion='FooBar GNU/Linux glibc build
|
|
|
|
|
123'}. The default value is @samp{GNU libc}.
|
|
|
|
|
|
|
|
|
|
@item --with-bugurl=@var{url}
|
|
|
|
|
Specify the URL that users should visit if they wish to report a bug,
|
|
|
|
|
to be included in @option{--help} output from programs installed with
|
|
|
|
|
@theglibc{}. The default value refers to the main bug-reporting
|
|
|
|
|
information for @theglibc{}.
|
2023-03-17 09:14:50 +00:00
|
|
|
|
|
|
|
|
@item --enable-fortify-source
|
|
|
|
|
@itemx --enable-fortify-source=@var{LEVEL}
|
|
|
|
|
Use -D_FORTIFY_SOURCE=@option{LEVEL} to control hardening in the GNU C Library.
|
|
|
|
|
If not provided, @option{LEVEL} defaults to highest possible value supported by
|
|
|
|
|
the build compiler.
|
|
|
|
|
|
|
|
|
|
Default is to disable fortification.
|
1998-03-17 17:27:52 +00:00
|
|
|
@end table
|
|
|
|
|
|
1998-11-04 23:04:21 +00:00
|
|
|
To build the library and related programs, type @code{make}. This will
|
|
|
|
|
produce a lot of output, some of which may look like errors from
|
2016-10-06 06:58:45 +00:00
|
|
|
@code{make} but aren't. Look for error messages from @code{make}
|
2002-04-03 09:17:17 +00:00
|
|
|
containing @samp{***}. Those indicate that something is seriously wrong.
|
1998-11-04 23:04:21 +00:00
|
|
|
|
2006-03-06 10:59:43 +00:00
|
|
|
The compilation process can take a long time, depending on the
|
|
|
|
|
configuration and the speed of your machine. Some complex modules may
|
|
|
|
|
take a very long time to compile, as much as several minutes on slower
|
|
|
|
|
machines. Do not panic if the compiler appears to hang.
|
1998-03-17 17:27:52 +00:00
|
|
|
|
2001-12-15 06:45:58 +00:00
|
|
|
If you want to run a parallel make, simply pass the @samp{-j} option
|
|
|
|
|
with an appropriate numeric parameter to @code{make}. You need a recent
|
|
|
|
|
GNU @code{make} version, though.
|
1998-04-21 09:43:11 +00:00
|
|
|
|
1999-08-27 19:06:58 +00:00
|
|
|
To build and run test programs which exercise some of the library
|
|
|
|
|
facilities, type @code{make check}. If it does not complete
|
|
|
|
|
successfully, do not use the built library, and report a bug after
|
|
|
|
|
verifying that the problem is not already known. @xref{Reporting Bugs},
|
|
|
|
|
for instructions on reporting bugs. Note that some of the tests assume
|
|
|
|
|
they are not being run by @code{root}. We recommend you compile and
|
2012-02-28 14:44:20 +00:00
|
|
|
test @theglibc{} as an unprivileged user.
|
1998-03-17 17:27:52 +00:00
|
|
|
|
2001-12-15 06:45:58 +00:00
|
|
|
Before reporting bugs make sure there is no problem with your system.
|
2002-04-03 09:17:17 +00:00
|
|
|
The tests (and later installation) use some pre-existing files of the
|
2001-12-15 06:45:58 +00:00
|
|
|
system such as @file{/etc/passwd}, @file{/etc/nsswitch.conf} and others.
|
|
|
|
|
These files must all contain correct and sensible content.
|
|
|
|
|
|
Do not terminate default test runs on test failure.
This patch is an updated version of
<https://sourceware.org/ml/libc-alpha/2014-01/msg00198.html> and
<https://sourceware.org/ml/libc-alpha/2014-03/msg00180.html>.
Normal practice for software testsuites is that rather than
terminating immediately when a test fails, they continue running and
report at the end on how many tests passed or failed.
The principle behind the glibc testsuite stopping on failure was
probably that the expected state is no failures and so any failure
indicates a problem such as miscompilation. In practice, while this
is fairly close to true for native testing on x86_64 and x86 (kernel
bugs and race conditions can still cause intermittent failures), it's
less likely to be the case on other platforms, and so people testing
glibc run the testsuite with "make -k" and then examine the logs to
determine whether the failures are what they expect to fail on that
platform, possibly with some automation for the comparison.
This patch switches the glibc testsuite to the normal convention of
not stopping on failure - unless you use stop-on-test-failure=y, in
which case it behaves essentially as it did before (and does not
generate overall test summaries on failure). Instead, the summary
tests.sum may contain tests that FAILed. At the end of the test run,
any FAIL or ERROR lines from tests.sum are printed, and then it exits
with error status if there were any such lines. In addition, build
failures will also cause the test run to stop - this has the
justification that those *do* indicate serious problems that should be
promptly fixed and aren't generally hard to fix (but apart from that,
avoiding the build stopping on those failures seems harder).
Note that unlike the previous patches in this series, this *does*
require people with automation around testing glibc to change their
processes - either to start using tests.sum / xtests.sum to track
failures and compare them with expectations (with or without also
using "make -k" and examining "make" logs to identify build failures),
or else to use stop-on-test-failure=y and ignore the new tests.sum /
xtests.sum mechanism. (If all you check is the exit status from "make
check", no changes are needed unless you want to avoid test runs
continuing after the first failure.)
Tested x86_64.
* scripts/evaluate-test.sh: Handle fourth argument to determine
whether test run should stop on failure.
* Makeconfig (stop-on-test-failure): New variable.
(evaluate-test): Pass fourth argument to evaluate-test.sh based on
$(stop-on-test-failure).
* Makefile (tests): Give a summary of results from testing and
exit with failure status if they include an ERROR or FAIL.
(xtests): Likewise.
* manual/install.texi (Configuring and compiling): Mention
stop-on-test-failure=y.
* INSTALL: Regenerated.
2014-03-14 21:02:40 +00:00
|
|
|
Normally, @code{make check} will run all the tests before reporting
|
|
|
|
|
all problems found and exiting with error status if any problems
|
|
|
|
|
occurred. You can specify @samp{stop-on-test-failure=y} when running
|
|
|
|
|
@code{make check} to make the test run stop and exit with an error
|
|
|
|
|
status immediately when a failure occurs.
|
|
|
|
|
|
1998-03-17 17:27:52 +00:00
|
|
|
To format the @cite{GNU C Library Reference Manual} for printing, type
|
2012-05-14 19:45:48 +00:00
|
|
|
@w{@code{make dvi}}. You need a working @TeX{} installation to do
|
|
|
|
|
this. The distribution builds the on-line formatted version of the
|
|
|
|
|
manual, as Info files, as part of the build process. You can build
|
|
|
|
|
them manually with @w{@code{make info}}.
|
1998-11-09 18:21:06 +00:00
|
|
|
|
2000-01-12 10:19:48 +00:00
|
|
|
The library has a number of special-purpose configuration parameters
|
|
|
|
|
which you can find in @file{Makeconfig}. These can be overwritten with
|
|
|
|
|
the file @file{configparms}. To change them, create a
|
|
|
|
|
@file{configparms} in your build directory and add values as appropriate
|
|
|
|
|
for your system. The file is included and parsed by @code{make} and has
|
|
|
|
|
to follow the conventions for makefiles.
|
|
|
|
|
|
2012-02-28 14:44:20 +00:00
|
|
|
It is easy to configure @theglibc{} for cross-compilation by
|
2000-01-12 10:19:48 +00:00
|
|
|
setting a few variables in @file{configparms}. Set @code{CC} to the
|
|
|
|
|
cross-compiler for the target you configured the library for; it is
|
|
|
|
|
important to use this same @code{CC} value when running
|
2018-02-15 23:48:47 +00:00
|
|
|
@code{configure}, like this: @samp{configure @var{target}
|
|
|
|
|
CC=@var{target}-gcc}. Set @code{BUILD_CC} to the compiler to use for programs
|
2002-04-03 09:17:17 +00:00
|
|
|
run on the build system as part of compiling the library. You may need to
|
2011-02-15 19:52:29 +00:00
|
|
|
set @code{AR} to cross-compiling versions of @code{ar}
|
|
|
|
|
if the native tools are not configured to work with
|
2012-10-25 19:17:45 +00:00
|
|
|
object files for the target you configured for. When cross-compiling
|
|
|
|
|
@theglibc{}, it may be tested using @samp{make check
|
|
|
|
|
test-wrapper="@var{srcdir}/scripts/cross-test-ssh.sh @var{hostname}"},
|
|
|
|
|
where @var{srcdir} is the absolute directory name for the main source
|
|
|
|
|
directory and @var{hostname} is the host name of a system that can run
|
|
|
|
|
the newly built binaries of @theglibc{}. The source and build
|
|
|
|
|
directories must be visible at the same locations on both the build
|
|
|
|
|
system and @var{hostname}.
|
2021-01-15 15:40:39 +00:00
|
|
|
The @samp{cross-test-ssh.sh} script requires @samp{flock} from
|
|
|
|
|
@samp{util-linux} to work when @var{glibc_test_allow_time_setting}
|
|
|
|
|
environment variable is set.
|
|
|
|
|
|
|
|
|
|
It is also possible to execute tests, which require setting the date on
|
|
|
|
|
the target machine. Following use cases are supported:
|
|
|
|
|
@itemize @bullet
|
|
|
|
|
@item
|
|
|
|
|
@code{GLIBC_TEST_ALLOW_TIME_SETTING} is set in the environment in
|
|
|
|
|
which eligible tests are executed and have the privilege to run
|
|
|
|
|
@code{clock_settime}. In this case, nothing prevents those tests from
|
|
|
|
|
running in parallel, so the caller shall assure that those tests
|
|
|
|
|
are serialized or provide a proper wrapper script for them.
|
|
|
|
|
|
|
|
|
|
@item
|
|
|
|
|
The @code{cross-test-ssh.sh} script is used and one passes the
|
|
|
|
|
@option{--allow-time-setting} flag. In this case, both sets
|
|
|
|
|
@code{GLIBC_TEST_ALLOW_TIME_SETTING} and serialization of test
|
|
|
|
|
execution are assured automatically.
|
|
|
|
|
@end itemize
|
2000-01-12 10:19:48 +00:00
|
|
|
|
2012-10-31 20:43:54 +00:00
|
|
|
In general, when testing @theglibc{}, @samp{test-wrapper} may be set
|
|
|
|
|
to the name and arguments of any program to run newly built binaries.
|
|
|
|
|
This program must preserve the arguments to the binary being run, its
|
Don't require test wrappers to preserve environment variables, use more consistent environment.
One wart in the original support for test wrappers for cross testing,
as noted in
<https://sourceware.org/ml/libc-alpha/2012-10/msg00722.html>, is the
requirement for test wrappers to pass a poorly-defined set of
environment variables from the build system to the system running the
glibc under test. Although some variables are passed explicitly via
$(test-wrapper-env), including LD_* variables that simply can't be
passed implicitly because of the side effects they'd have on the build
system's dynamic linker, others are passed implicitly, including
variables such as GCONV_PATH and LOCPATH that could potentially affect
the build system's libc (so effectively relying on any such effects
not breaking the wrappers). In addition, the code in
cross-test-ssh.sh for preserving environment variables is fragile (it
depends on how bash formats a list of exported variables, and could
well break for multi-line variable definitions where the contents
contain things looking like other variable definitions).
This patch moves to explicitly passing environment variables via
$(test-wrapper-env). Makefile variables that previously used
$(test-wrapper) are split up into -before-env and -after-env parts
that can be passed separately to the various .sh files used in
testing, so those files can then insert environment settings between
the two parts.
The common default environment settings in make-test-out are made into
a separate makefile variable that can also be passed to scripts,
rather than many scripts duplicating those settings (for testing an
installed glibc, it is desirable to have the GCONV_PATH setting on
just one place, so just that one place needs to support it pointing to
an installed sysroot instead of the build tree). The default settings
are included in the variables such as $(test-program-prefix), so that
if tests do not need any non-default settings they can continue to use
single variables rather than the split-up variables.
Although this patch cleans up LC_ALL=C settings (that being part of
the common defaults), various LANG=C and LANGUAGE=C settings remain.
Those are generally unnecessary and I propose a subsequent cleanup to
remove them. LC_ALL takes precedence over LANG, and while LANGUAGE
takes precedence over LC_ALL, it only does so for settings other than
LC_ALL=C. So LC_ALL=C on its own is sufficient to ensure the C
locale, and anything that gets LC_ALL=C does not need the other
settings.
While preparing this patch I noticed some tests with .sh files that
appeared to do nothing beyond what the generic makefile support for
tests can do (localedata/tst-wctype.sh - the makefiles support -ENV
variables and .input files - and localedata/tst-mbswcs.sh - just runs
five tests that could be run individually from the makefile). So I
propose another subsequent cleanup to move those to using the generic
support instead of special .sh files.
Tested x86_64 (native) and powerpc32 (cross).
* Makeconfig (run-program-env): New variable.
(run-program-prefix-before-env): Likewise.
(run-program-prefix-after-env): Likewise.
(run-program-prefix): Define in terms of new variables.
(built-program-cmd-before-env): New variable.
(built-program-cmd-after-env): Likewise.
(built-program-cmd): Define in terms of new variables.
(test-program-prefix-before-env): New variable.
(test-program-prefix-after-env): Likewise.
(test-program-prefix): Define in terms of new variables.
(test-program-cmd-before-env): New variable.
(test-program-cmd-after-env): Likewise.
(test-program-cmd): Define in terms of new variables.
* Rules (make-test-out): Use $(run-program-env).
* scripts/cross-test-ssh.sh (env_blacklist): Remove variable.
(help): Do not mention environment variables. Mention
--timeoutfactor option.
(timeoutfactor): New variable.
(blacklist_exports): Remove function.
(exports): Remove variable.
(command): Do not include ${exports}.
* manual/install.texi (Configuring and compiling): Do not mention
test wrappers preserving environment variables. Mention that last
assignment to a variable must take precedence.
* INSTALL: Regenerated.
* benchtests/Makefile (run-bench): Use $(run-program-env).
* catgets/Makefile ($(objpfx)test1.cat): Use
$(built-program-cmd-before-env), $(run-program-env) and
$(built-program-cmd-after-env).
($(objpfx)test2.cat): Do not specify environment variables
explicitly.
($(objpfx)de/libc.cat): Use $(built-program-cmd-before-env),
$(run-program-env) and $(built-program-cmd-after-env).
($(objpfx)test-gencat.out): Use $(test-program-cmd-before-env),
$(run-program-env) and $(test-program-cmd-after-env).
($(objpfx)sample.SJIS.cat): Do not specify environment variables
explicitly.
* catgets/test-gencat.sh: Use test_program_cmd_before_env,
run_program_env and test_program_cmd_after_env arguments.
* elf/Makefile ($(objpfx)tst-pathopt.out): Use $(run-program-env).
* elf/tst-pathopt.sh: Use run_program_env argument.
* iconvdata/Makefile ($(objpfx)iconv-test.out): Use
$(test-wrapper-env) and $(run-program-env).
* iconvdata/run-iconv-test.sh: Use test_wrapper_env and
run_program_env arguments.
* iconvdata/tst-table.sh: Do not set GCONV_PATH explicitly.
* intl/Makefile ($(objpfx)tst-gettext.out): Use
$(test-program-prefix-before-env), $(run-program-env) and
$(test-program-prefix-after-env).
($(objpfx)tst-gettext2.out): Likewise.
* intl/tst-gettext.sh: Use test_program_prefix_before_env,
run_program_env and test_program_prefix_after_env arguments.
* intl/tst-gettext2.sh: Likewise.
* intl/tst-gettext4.sh: Do not set environment variables
explicitly.
* intl/tst-gettext6.sh: Likewise.
* intl/tst-translit.sh: Likewise.
* malloc/Makefile ($(objpfx)tst-mtrace.out): Use
$(test-program-prefix-before-env), $(run-program-env) and
$(test-program-prefix-after-env).
* malloc/tst-mtrace.sh: Use test_program_prefix_before_env,
run_program_env and test_program_prefix_after_env arguments.
* math/Makefile (run-regen-ulps): Use $(run-program-env).
* nptl/Makefile ($(objpfx)tst-tls6.out): Use $(run-program-env).
* nptl/tst-tls6.sh: Use run_program_env argument. Set LANG=C
explicitly with each use of ${test_wrapper_env}.
* posix/Makefile ($(objpfx)wordexp-tst.out): Use
$(test-program-prefix-before-env), $(run-program-env) and
$(test-program-prefix-after-env).
* posix/tst-getconf.sh: Do not set environment variables
explicitly.
* posix/wordexp-tst.sh: Use test_program_prefix_before_env,
run_program_env and test_program_prefix_after_env arguments.
* stdio-common/tst-printf.sh: Do not set environment variables
explicitly.
* stdlib/Makefile ($(objpfx)tst-fmtmsg.out): Use
$(test-program-prefix-before-env), $(run-program-env) and
$(test-program-prefix-after-env).
* stdlib/tst-fmtmsg.sh: Use test_program_prefix_before_env,
run_program_env and test_program_prefix_after_env arguments.
Split $test calls into $test_pre and $test.
* timezone/Makefile (build-testdata): Use
$(built-program-cmd-before-env), $(run-program-env) and
$(built-program-cmd-after-env).
localedata/ChangeLog:
* Makefile ($(addprefix $(objpfx),$(CTYPE_FILES))): Use
$(built-program-cmd-before-env), $(run-program-env) and
$(built-program-cmd-after-env).
($(objpfx)sort-test.out): Use $(test-program-prefix-before-env),
$(run-program-env) and $(test-program-prefix-after-env).
($(objpfx)tst-fmon.out): Use $(run-program-prefix-before-env),
$(run-program-env) and $(run-program-prefix-after-env).
($(objpfx)tst-locale.out): Use $(built-program-cmd-before-env),
$(run-program-env) and $(built-program-cmd-after-env).
($(objpfx)tst-trans.out): Use $(run-program-prefix-before-env),
$(run-program-env), $(run-program-prefix-after-env),
$(test-program-prefix-before-env) and
$(test-program-prefix-after-env).
($(objpfx)tst-ctype.out): Use $(test-program-cmd-before-env),
$(run-program-env) and $(test-program-cmd-after-env).
($(objpfx)tst-wctype.out): Likewise.
($(objpfx)tst-langinfo.out): Likewise.
($(objpfx)tst-langinfo-static.out): Likewise.
* gen-locale.sh: Use localedef_before_env, run_program_env and
localedef_after_env arguments.
* sort-test.sh: Use test_program_prefix_before_env,
run_program_env and test_program_prefix_after_env arguments.
* tst-ctype.sh: Use tst_ctype_before_env, run_program_env and
tst_ctype_after_env arguments.
* tst-fmon.sh: Use run_program_prefix_before_env, run_program_env
and run_program_prefix_after_env arguments.
* tst-langinfo.sh: Use tst_langinfo_before_env, run_program_env
and tst_langinfo_after_env arguments.
* tst-locale.sh: Use localedef_before_env, run_program_env and
localedef_after_env arguments.
* tst-mbswcs.sh: Do not set environment variables explicitly.
* tst-numeric.sh: Likewise.
* tst-rpmatch.sh: Likewise.
* tst-trans.sh: Use run_program_prefix_before_env,
run_program_env, run_program_prefix_after_env,
test_program_prefix_before_env and test_program_prefix_after_env
arguments.
* tst-wctype.sh: Use tst_wctype_before_env, run_program_env and
tst_wctype_after_env arguments.
2014-06-06 22:19:27 +00:00
|
|
|
working directory and the standard input, output and error file
|
2015-03-06 18:59:15 +00:00
|
|
|
descriptors. If @samp{@var{test-wrapper} env} will not work to run a
|
|
|
|
|
program with environment variables set, then @samp{test-wrapper-env}
|
|
|
|
|
must be set to a program that runs a newly built program with
|
|
|
|
|
environment variable assignments in effect, those assignments being
|
|
|
|
|
specified as @samp{@var{var}=@var{value}} before the name of the
|
|
|
|
|
program to be run. If multiple assignments to the same variable are
|
|
|
|
|
specified, the last assignment specified must take precedence.
|
|
|
|
|
Similarly, if @samp{@var{test-wrapper} env -i} will not work to run a
|
|
|
|
|
program with an environment completely empty of variables except those
|
|
|
|
|
directly assigned, then @samp{test-wrapper-env-only} must be set; its
|
|
|
|
|
use has the same syntax as @samp{test-wrapper-env}, the only
|
|
|
|
|
difference in its semantics being starting with an empty set of
|
|
|
|
|
environment variables rather than the ambient set.
|
2012-10-31 20:43:54 +00:00
|
|
|
|
2021-05-20 07:34:37 +00:00
|
|
|
For AArch64 with SVE, when testing @theglibc{}, @samp{test-wrapper}
|
|
|
|
|
may be set to "@var{srcdir}/sysdeps/unix/sysv/linux/aarch64/vltest.py
|
|
|
|
|
@var{vector-length}" to change Vector Length.
|
2000-01-12 10:19:48 +00:00
|
|
|
|
1998-11-12 18:03:43 +00:00
|
|
|
@node Running make install
|
1998-11-09 18:21:06 +00:00
|
|
|
@appendixsec Installing the C Library
|
|
|
|
|
@cindex installing
|
1998-03-17 17:27:52 +00:00
|
|
|
|
|
|
|
|
To install the library and its header files, and the Info files of the
|
2014-06-07 19:58:36 +00:00
|
|
|
manual, type @code{make install}. This will
|
2002-04-03 09:17:17 +00:00
|
|
|
build things, if necessary, before installing them; however, you should
|
2012-02-28 14:44:20 +00:00
|
|
|
still compile everything first. If you are installing @theglibc{} as your
|
2000-11-10 05:00:25 +00:00
|
|
|
primary C library, we recommend that you shut the system down to
|
|
|
|
|
single-user mode first, and reboot afterward. This minimizes the risk
|
|
|
|
|
of breaking things when the library changes out from underneath.
|
1998-11-09 18:21:06 +00:00
|
|
|
|
2012-02-18 18:31:53 +00:00
|
|
|
@samp{make install} will do the entire job of upgrading from a
|
2012-02-28 14:44:20 +00:00
|
|
|
previous installation of @theglibc{} version 2.x. There may sometimes
|
|
|
|
|
be headers
|
2012-02-18 18:31:53 +00:00
|
|
|
left behind from the previous installation, but those are generally
|
|
|
|
|
harmless. If you want to avoid leaving headers behind you can do
|
|
|
|
|
things in the following order.
|
1999-11-25 19:27:07 +00:00
|
|
|
|
|
|
|
|
You must first build the library (@samp{make}), optionally check it
|
|
|
|
|
(@samp{make check}), switch the include directories and then install
|
|
|
|
|
(@samp{make install}). The steps must be done in this order. Not moving
|
|
|
|
|
the directory before install will result in an unusable mixture of header
|
|
|
|
|
files from both libraries, but configuring, building, and checking the
|
|
|
|
|
library requires the ability to compile and run programs against the old
|
2012-02-18 18:31:53 +00:00
|
|
|
library. The new @file{/usr/include}, after switching the include
|
|
|
|
|
directories and before installing the library should contain the Linux
|
|
|
|
|
headers, but nothing else. If you do this, you will need to restore
|
2012-02-28 14:44:20 +00:00
|
|
|
any headers from libraries other than @theglibc{} yourself after installing the
|
2000-03-26 06:03:42 +00:00
|
|
|
library.
|
1999-11-25 19:27:07 +00:00
|
|
|
|
2015-06-12 19:15:57 +00:00
|
|
|
You can install @theglibc{} somewhere other than where you configured
|
|
|
|
|
it to go by setting the @code{DESTDIR} GNU standard make variable on
|
|
|
|
|
the command line for @samp{make install}. The value of this variable
|
|
|
|
|
is prepended to all the paths for installation. This is useful when
|
|
|
|
|
setting up a chroot environment or preparing a binary distribution.
|
|
|
|
|
The directory should be specified with an absolute file name. Installing
|
|
|
|
|
with the @code{prefix} and @code{exec_prefix} GNU standard make variables
|
|
|
|
|
set is not supported.
|
1998-11-09 18:21:06 +00:00
|
|
|
|
2012-02-28 14:44:20 +00:00
|
|
|
@Theglibc{} includes a daemon called @code{nscd}, which you
|
1998-11-09 18:21:06 +00:00
|
|
|
may or may not want to run. @code{nscd} caches name service lookups; it
|
|
|
|
|
can dramatically improve performance with NIS+, and may help with DNS as
|
2000-04-21 03:43:31 +00:00
|
|
|
well.
|
1998-11-09 18:21:06 +00:00
|
|
|
|
|
|
|
|
One auxiliary program, @file{/usr/libexec/pt_chown}, is installed setuid
|
2013-09-10 04:09:27 +00:00
|
|
|
@code{root} if the @samp{--enable-pt_chown} configuration option is used.
|
|
|
|
|
This program is invoked by the @code{grantpt} function; it sets the
|
|
|
|
|
permissions on a pseudoterminal so it can be used by the calling process.
|
|
|
|
|
If you are using a Linux kernel with the @code{devpts} filesystem enabled
|
|
|
|
|
and mounted at @file{/dev/pts}, you don't need this program.
|
1998-03-17 17:27:52 +00:00
|
|
|
|
Modernize and fix doc’s “Date and Time” (BZ 31876)
POSIX.1-2024 (now official) specifies tm_gmtoff and tm_zone.
This is a good time to update the manual’s “Date and Time”
chapter so I went through it, fixed some outdated
stuff that had been in there for decades, and improved it to match
POSIX.1-2024 better and to clarify some implementation-defined
behavior. Glibc already conforms to POSIX.1-2024 in these matters, so
this is merely a documentation change.
* manual/examples/strftim.c: Use snprintf instead of now-deprecated
function asctime. Check for localtime failure. Simplify by using
puts instead of fputs. Prefer ‘buf, sizeof buf’ to less-obvious
‘buffer, SIZE’.
* manual/examples/timespec_subtract.c: Modernize to use struct
timespec not struct timeval, and rename from timeval_subtract.c.
All uses changed. Check for overflow. Do not check for negative
return value, which ought to be OK since negative time_t is OK.
Use GNU indenting style.
* manual/time.texi:
Document CLOCKS_PER_SEC, TIME_UTC, timespec_get, timespec_getres,
strftime_l.
Document the storage lifetime of tm_zone and of tzname.
Caution against use of tzname, timezone and daylight, saying that
these variables have unspecified values when TZ is geographic.
This is what glibc actually does (contrary to what the manual said
before this patch), and POSIX is planned to say the same thing
<https://austingroupbugs.net/view.php?id=1816>.
Also say that directly accessing the variables is not thread-safe.
Say that localtime_r and ctime_r don’t necessarily set time zone
state. Similarly, in the tzset documentation, say that it is called
by ctime, localtime, mktime, strftime, not that it is called by all
time conversion functions that depend on the time zone.
Say that tm_isdst is useful mostly just for mktime, and that
other uses should prefer tm_gmtoff and tm_zone instead.
Do not say that strftime ignores tm_gmtoff and tm_zone, because
it doesn’t do that.
Document what gmtime does to tm_gmtoff and tm_zone.
Say that the asctime, asctime_r, ctime, and ctime_r are now deprecated
and/or obsolescent, and that behavior is undefined if the year is <
1000 or > 9999. Document strftime before these now-obsolescent
functions, so that readers see the useful function first.
Coin the terms “geographical format” and “proleptic format” for the
two main formats of TZ settings, to simplify exposition. Use this
wording consistently.
Update top-level proleptic syntax to match POSIX.1-2024, which glibc
already implements. Document the angle-bracket quoted forms of time
zone abbreviations in proleptic TZ. Say that time zone abbreviations
can contain only ASCII alphanumerics, ‘+’, and ‘-’.
Document what happens if the proleptic form specifies a DST
abbreviation and offset but omits the rules. POSIX says this is
implementation-defined so we need to document it. Although this
documentation mentions ‘posixrules’ tersely, we need to rethink
‘posixrules’ since I think it stops working after 2038.
Clarify wording about TZ settings beginning with ‘;’.
Say that timegm is in ISO C (as of C23).
Say that POSIX.1-2024 removed gettimeofday.
Say that tm_gmtoff and tm_zone are extensions to ISO C, which is
clearer than saying they are invisible in a struct ISO C enviroment,
and gives us more wiggle room if we want to make them visible in
strict ISO C, something that ISO C allows.
Drop mention of old standards like POSIX.1c and POSIX.2-1992 in the
text when the history is so old that it’s no longer useful in a
general-purpose manual.
Define Coordinated Universal Time (UTC), time zone, time zone ruleset,
and POSIX Epoch, and use these phrases more consistently.
Improve TZ examples to show more variety, and to reflect current
practice and timestamps. Remove obsolete example about Argentina.
Add an example for Ireland.
Don’t rely on GCC extensions when explaining ctime_r.
Do not say that difftime produces the mathematically correct result,
since it might be inexact.
For clock_t don’t say “as in the example above” when there is no
such example, and don’t say that casting to double works “properly
and consistently no matter what”, as it suffers from rounding and
overflow.
Don’t say broken-down time is not useful for calculations; it’s
merely painful.
Say that UTC is not defined before 1960.
Rename Time Zone Functions to Time Zone State. All uses changed.
Update Internet RFC 822 → 5322, 1305 → 5905. Drop specific years of
ISO 8601 as they don’t matter.
Minor style changes: @code{"..."} → @t{"..."} to avoid overquoting in
info files, @code → @env for environment variables, Daylight Saving
Time → daylight saving time, white space → whitespace, prime meridian
→ Prime Meridian.
2024-06-08 16:48:25 +00:00
|
|
|
After installation you should configure the time zone ruleset and install
|
|
|
|
|
locales for your system. The time zone ruleset ensures that timestamps
|
|
|
|
|
are processed correctly for your location. The locales ensure that
|
2018-07-26 14:14:55 +00:00
|
|
|
the display of information on your system matches the expectations of
|
|
|
|
|
your language and geographic region.
|
|
|
|
|
|
|
|
|
|
@Theglibc{} is able to use two kinds of localization information sources, the
|
|
|
|
|
first is a locale database named @file{locale-archive} which is generally
|
|
|
|
|
installed as @file{/usr/lib/locale/locale-archive}. The locale archive has the
|
|
|
|
|
benefit of taking up less space and being very fast to load, but only if you
|
|
|
|
|
plan to install sixty or more locales. If you plan to install one or two
|
|
|
|
|
locales you can instead install individual locales into their self-named
|
|
|
|
|
directories e.g.@: @file{/usr/lib/locale/en_US.utf8}. For example to install
|
|
|
|
|
the German locale using the character set for UTF-8 with name @code{de_DE} into
|
|
|
|
|
the locale archive issue the command @samp{localedef -i de_DE -f UTF-8 de_DE},
|
|
|
|
|
and to install just the one locale issue the command @samp{localedef
|
|
|
|
|
--no-archive -i de_DE -f UTF-8 de_DE}. To configure all locales that are
|
|
|
|
|
supported by @theglibc{}, you can issue from your build directory the command
|
|
|
|
|
@samp{make localedata/install-locales} to install all locales into the locale
|
|
|
|
|
archive or @samp{make localedata/install-locale-files} to install all locales
|
|
|
|
|
as files in the default configured locale installation directory (derived from
|
|
|
|
|
@samp{--prefix} or @code{--localedir}). To install into an alternative system
|
|
|
|
|
root use @samp{DESTDIR} e.g.@: @samp{make localedata/install-locale-files
|
|
|
|
|
DESTDIR=/opt/glibc}, but note that this does not change the configured prefix.
|
1999-08-28 22:34:29 +00:00
|
|
|
|
Modernize and fix doc’s “Date and Time” (BZ 31876)
POSIX.1-2024 (now official) specifies tm_gmtoff and tm_zone.
This is a good time to update the manual’s “Date and Time”
chapter so I went through it, fixed some outdated
stuff that had been in there for decades, and improved it to match
POSIX.1-2024 better and to clarify some implementation-defined
behavior. Glibc already conforms to POSIX.1-2024 in these matters, so
this is merely a documentation change.
* manual/examples/strftim.c: Use snprintf instead of now-deprecated
function asctime. Check for localtime failure. Simplify by using
puts instead of fputs. Prefer ‘buf, sizeof buf’ to less-obvious
‘buffer, SIZE’.
* manual/examples/timespec_subtract.c: Modernize to use struct
timespec not struct timeval, and rename from timeval_subtract.c.
All uses changed. Check for overflow. Do not check for negative
return value, which ought to be OK since negative time_t is OK.
Use GNU indenting style.
* manual/time.texi:
Document CLOCKS_PER_SEC, TIME_UTC, timespec_get, timespec_getres,
strftime_l.
Document the storage lifetime of tm_zone and of tzname.
Caution against use of tzname, timezone and daylight, saying that
these variables have unspecified values when TZ is geographic.
This is what glibc actually does (contrary to what the manual said
before this patch), and POSIX is planned to say the same thing
<https://austingroupbugs.net/view.php?id=1816>.
Also say that directly accessing the variables is not thread-safe.
Say that localtime_r and ctime_r don’t necessarily set time zone
state. Similarly, in the tzset documentation, say that it is called
by ctime, localtime, mktime, strftime, not that it is called by all
time conversion functions that depend on the time zone.
Say that tm_isdst is useful mostly just for mktime, and that
other uses should prefer tm_gmtoff and tm_zone instead.
Do not say that strftime ignores tm_gmtoff and tm_zone, because
it doesn’t do that.
Document what gmtime does to tm_gmtoff and tm_zone.
Say that the asctime, asctime_r, ctime, and ctime_r are now deprecated
and/or obsolescent, and that behavior is undefined if the year is <
1000 or > 9999. Document strftime before these now-obsolescent
functions, so that readers see the useful function first.
Coin the terms “geographical format” and “proleptic format” for the
two main formats of TZ settings, to simplify exposition. Use this
wording consistently.
Update top-level proleptic syntax to match POSIX.1-2024, which glibc
already implements. Document the angle-bracket quoted forms of time
zone abbreviations in proleptic TZ. Say that time zone abbreviations
can contain only ASCII alphanumerics, ‘+’, and ‘-’.
Document what happens if the proleptic form specifies a DST
abbreviation and offset but omits the rules. POSIX says this is
implementation-defined so we need to document it. Although this
documentation mentions ‘posixrules’ tersely, we need to rethink
‘posixrules’ since I think it stops working after 2038.
Clarify wording about TZ settings beginning with ‘;’.
Say that timegm is in ISO C (as of C23).
Say that POSIX.1-2024 removed gettimeofday.
Say that tm_gmtoff and tm_zone are extensions to ISO C, which is
clearer than saying they are invisible in a struct ISO C enviroment,
and gives us more wiggle room if we want to make them visible in
strict ISO C, something that ISO C allows.
Drop mention of old standards like POSIX.1c and POSIX.2-1992 in the
text when the history is so old that it’s no longer useful in a
general-purpose manual.
Define Coordinated Universal Time (UTC), time zone, time zone ruleset,
and POSIX Epoch, and use these phrases more consistently.
Improve TZ examples to show more variety, and to reflect current
practice and timestamps. Remove obsolete example about Argentina.
Add an example for Ireland.
Don’t rely on GCC extensions when explaining ctime_r.
Do not say that difftime produces the mathematically correct result,
since it might be inexact.
For clock_t don’t say “as in the example above” when there is no
such example, and don’t say that casting to double works “properly
and consistently no matter what”, as it suffers from rounding and
overflow.
Don’t say broken-down time is not useful for calculations; it’s
merely painful.
Say that UTC is not defined before 1960.
Rename Time Zone Functions to Time Zone State. All uses changed.
Update Internet RFC 822 → 5322, 1305 → 5905. Drop specific years of
ISO 8601 as they don’t matter.
Minor style changes: @code{"..."} → @t{"..."} to avoid overquoting in
info files, @code → @env for environment variables, Daylight Saving
Time → daylight saving time, white space → whitespace, prime meridian
→ Prime Meridian.
2024-06-08 16:48:25 +00:00
|
|
|
To configure the time zone ruleset, set the @code{TZ} environment
|
2002-04-03 09:17:17 +00:00
|
|
|
variable. The script @code{tzselect} helps you to select the right value.
|
|
|
|
|
As an example, for Germany, @code{tzselect} would tell you to use
|
|
|
|
|
@samp{TZ='Europe/Berlin'}. For a system wide installation (the given
|
|
|
|
|
paths are for an installation with @samp{--prefix=/usr}), link the
|
Modernize and fix doc’s “Date and Time” (BZ 31876)
POSIX.1-2024 (now official) specifies tm_gmtoff and tm_zone.
This is a good time to update the manual’s “Date and Time”
chapter so I went through it, fixed some outdated
stuff that had been in there for decades, and improved it to match
POSIX.1-2024 better and to clarify some implementation-defined
behavior. Glibc already conforms to POSIX.1-2024 in these matters, so
this is merely a documentation change.
* manual/examples/strftim.c: Use snprintf instead of now-deprecated
function asctime. Check for localtime failure. Simplify by using
puts instead of fputs. Prefer ‘buf, sizeof buf’ to less-obvious
‘buffer, SIZE’.
* manual/examples/timespec_subtract.c: Modernize to use struct
timespec not struct timeval, and rename from timeval_subtract.c.
All uses changed. Check for overflow. Do not check for negative
return value, which ought to be OK since negative time_t is OK.
Use GNU indenting style.
* manual/time.texi:
Document CLOCKS_PER_SEC, TIME_UTC, timespec_get, timespec_getres,
strftime_l.
Document the storage lifetime of tm_zone and of tzname.
Caution against use of tzname, timezone and daylight, saying that
these variables have unspecified values when TZ is geographic.
This is what glibc actually does (contrary to what the manual said
before this patch), and POSIX is planned to say the same thing
<https://austingroupbugs.net/view.php?id=1816>.
Also say that directly accessing the variables is not thread-safe.
Say that localtime_r and ctime_r don’t necessarily set time zone
state. Similarly, in the tzset documentation, say that it is called
by ctime, localtime, mktime, strftime, not that it is called by all
time conversion functions that depend on the time zone.
Say that tm_isdst is useful mostly just for mktime, and that
other uses should prefer tm_gmtoff and tm_zone instead.
Do not say that strftime ignores tm_gmtoff and tm_zone, because
it doesn’t do that.
Document what gmtime does to tm_gmtoff and tm_zone.
Say that the asctime, asctime_r, ctime, and ctime_r are now deprecated
and/or obsolescent, and that behavior is undefined if the year is <
1000 or > 9999. Document strftime before these now-obsolescent
functions, so that readers see the useful function first.
Coin the terms “geographical format” and “proleptic format” for the
two main formats of TZ settings, to simplify exposition. Use this
wording consistently.
Update top-level proleptic syntax to match POSIX.1-2024, which glibc
already implements. Document the angle-bracket quoted forms of time
zone abbreviations in proleptic TZ. Say that time zone abbreviations
can contain only ASCII alphanumerics, ‘+’, and ‘-’.
Document what happens if the proleptic form specifies a DST
abbreviation and offset but omits the rules. POSIX says this is
implementation-defined so we need to document it. Although this
documentation mentions ‘posixrules’ tersely, we need to rethink
‘posixrules’ since I think it stops working after 2038.
Clarify wording about TZ settings beginning with ‘;’.
Say that timegm is in ISO C (as of C23).
Say that POSIX.1-2024 removed gettimeofday.
Say that tm_gmtoff and tm_zone are extensions to ISO C, which is
clearer than saying they are invisible in a struct ISO C enviroment,
and gives us more wiggle room if we want to make them visible in
strict ISO C, something that ISO C allows.
Drop mention of old standards like POSIX.1c and POSIX.2-1992 in the
text when the history is so old that it’s no longer useful in a
general-purpose manual.
Define Coordinated Universal Time (UTC), time zone, time zone ruleset,
and POSIX Epoch, and use these phrases more consistently.
Improve TZ examples to show more variety, and to reflect current
practice and timestamps. Remove obsolete example about Argentina.
Add an example for Ireland.
Don’t rely on GCC extensions when explaining ctime_r.
Do not say that difftime produces the mathematically correct result,
since it might be inexact.
For clock_t don’t say “as in the example above” when there is no
such example, and don’t say that casting to double works “properly
and consistently no matter what”, as it suffers from rounding and
overflow.
Don’t say broken-down time is not useful for calculations; it’s
merely painful.
Say that UTC is not defined before 1960.
Rename Time Zone Functions to Time Zone State. All uses changed.
Update Internet RFC 822 → 5322, 1305 → 5905. Drop specific years of
ISO 8601 as they don’t matter.
Minor style changes: @code{"..."} → @t{"..."} to avoid overquoting in
info files, @code → @env for environment variables, Daylight Saving
Time → daylight saving time, white space → whitespace, prime meridian
→ Prime Meridian.
2024-06-08 16:48:25 +00:00
|
|
|
time zone file which is in @file{/usr/share/zoneinfo} to the file
|
1999-08-28 22:34:29 +00:00
|
|
|
@file{/etc/localtime}. For Germany, you might execute @samp{ln -s
|
|
|
|
|
/usr/share/zoneinfo/Europe/Berlin /etc/localtime}.
|
|
|
|
|
|
1998-11-04 23:04:21 +00:00
|
|
|
@node Tools for Compilation
|
|
|
|
|
@appendixsec Recommended Tools for Compilation
|
1998-03-17 17:27:52 +00:00
|
|
|
@cindex installation tools
|
|
|
|
|
@cindex tools, for installing library
|
|
|
|
|
|
|
|
|
|
We recommend installing the following GNU tools before attempting to
|
2012-02-28 14:44:20 +00:00
|
|
|
build @theglibc{}:
|
1998-03-17 17:27:52 +00:00
|
|
|
|
|
|
|
|
@itemize @bullet
|
|
|
|
|
@item
|
2018-07-04 13:27:24 +00:00
|
|
|
GNU @code{make} 4.0 or newer
|
1998-03-17 17:27:52 +00:00
|
|
|
|
2024-01-30 23:13:43 +00:00
|
|
|
As of release time, GNU @code{make} 4.4.1 is the newest verified to work
|
2018-07-31 20:37:07 +00:00
|
|
|
to build @theglibc{}.
|
|
|
|
|
|
1998-03-17 17:27:52 +00:00
|
|
|
@item
|
2019-02-01 16:27:44 +00:00
|
|
|
GCC 6.2 or newer
|
2012-02-27 23:07:59 +00:00
|
|
|
|
2019-02-01 16:27:44 +00:00
|
|
|
GCC 6.2 or higher is required. In general it is recommended to use
|
2014-11-14 18:00:34 +00:00
|
|
|
the newest version of the compiler that is known to work for building
|
|
|
|
|
@theglibc{}, as newer compilers usually produce better code. As of
|
2024-07-20 22:27:35 +00:00
|
|
|
release time, GCC 14.1 is the newest compiler verified to work to build
|
2014-11-14 18:00:34 +00:00
|
|
|
@theglibc{}.
|
1999-03-10 16:08:03 +00:00
|
|
|
|
powerpc64le: raise GCC requirement to 7.4 for long double transition
Add compiler feature tests to ensure we can build ieee128 long double.
These test for -mabi=ieeelongdouble, -mno-gnu-attribute, and -Wno-psabi.
Likewise, verify some compiler bugs have been addressed. These aren't
helpful for building glibc, but may cause test failures when testing
the new long double. See notes below from Raji.
On powerpc64le, some older compiler versions give error for the function
signbit() for 128-bit floating point types. This is fixed by PR83862
in gcc 8.0 and backported to gcc6 and gcc7. This patch adds a test
to check compiler version to avoid compiler errors during make check.
Likewise, test for -mno-gnu-attribute support which was
On powerpc64le, a few files are built on IEEE long double mode
(-mabi=ieeelongdouble), whereas most are built on IBM long double mode
(-mabi=ibmlongdouble, the default for -mlong-double-128). Since binutils
2.31, linking object files with different long double modes causes
errors similar to:
ld: libc_pic.a(s_isinfl.os) uses IBM long double,
libc_pic.a(ieee128-qefgcvt.os) uses IEEE long double.
collect2: error: ld returned 1 exit status
make[2]: *** [../Makerules:649: libc_pic.os] Error 1
The warnings are fair and correct, but in order for glibc to have
support for both long double modes on powerpc64le, they have to be
ignored. This can be accomplished with the use of -mno-gnu-attribute
option when building the few files that require IEEE long double mode.
However, -mno-gnu-attribute is not available in GCC 6, the minimum
version required to build glibc, so this patch adds a test for this
feature in powerpc64le builds, and fails early if it's not available.
Co-Authored-By: Rajalakshmi Srinivasaraghavan <raji@linux.vnet.ibm.com>
Co-Authored-By: Gabriel F. T. Gomes <gabrielftg@linux.ibm.com>
Reviewed-by: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
2020-02-07 20:08:23 +00:00
|
|
|
For PowerPC 64-bits little-endian (powerpc64le), a GCC version with support
|
|
|
|
|
for @option{-mno-gnu-attribute}, @option{-mabi=ieeelongdouble}, and
|
2023-07-13 19:49:17 +00:00
|
|
|
@option{-mabi=ibmlongdouble} is required. Likewise, the compiler must also
|
2020-03-17 13:38:54 +00:00
|
|
|
support passing @option{-mlong-double-128} with the preceding options. As
|
|
|
|
|
of release, this implies GCC 7.4 and newer (excepting GCC 7.5.0, see GCC
|
|
|
|
|
PR94200). These additional features are required for building the GNU C
|
|
|
|
|
Library with support for IEEE long double.
|
|
|
|
|
|
|
|
|
|
@c powerpc64le performs an autoconf test to verify the compiler compiles with
|
|
|
|
|
@c commands like "$CC -c foo.c -mabi=ibmlongdouble -mlong-double-128".
|
powerpc64le: raise GCC requirement to 7.4 for long double transition
Add compiler feature tests to ensure we can build ieee128 long double.
These test for -mabi=ieeelongdouble, -mno-gnu-attribute, and -Wno-psabi.
Likewise, verify some compiler bugs have been addressed. These aren't
helpful for building glibc, but may cause test failures when testing
the new long double. See notes below from Raji.
On powerpc64le, some older compiler versions give error for the function
signbit() for 128-bit floating point types. This is fixed by PR83862
in gcc 8.0 and backported to gcc6 and gcc7. This patch adds a test
to check compiler version to avoid compiler errors during make check.
Likewise, test for -mno-gnu-attribute support which was
On powerpc64le, a few files are built on IEEE long double mode
(-mabi=ieeelongdouble), whereas most are built on IBM long double mode
(-mabi=ibmlongdouble, the default for -mlong-double-128). Since binutils
2.31, linking object files with different long double modes causes
errors similar to:
ld: libc_pic.a(s_isinfl.os) uses IBM long double,
libc_pic.a(ieee128-qefgcvt.os) uses IEEE long double.
collect2: error: ld returned 1 exit status
make[2]: *** [../Makerules:649: libc_pic.os] Error 1
The warnings are fair and correct, but in order for glibc to have
support for both long double modes on powerpc64le, they have to be
ignored. This can be accomplished with the use of -mno-gnu-attribute
option when building the few files that require IEEE long double mode.
However, -mno-gnu-attribute is not available in GCC 6, the minimum
version required to build glibc, so this patch adds a test for this
feature in powerpc64le builds, and fails early if it's not available.
Co-Authored-By: Rajalakshmi Srinivasaraghavan <raji@linux.vnet.ibm.com>
Co-Authored-By: Gabriel F. T. Gomes <gabrielftg@linux.ibm.com>
Reviewed-by: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
2020-02-07 20:08:23 +00:00
|
|
|
|
2017-11-20 20:46:17 +00:00
|
|
|
For ARC architecture builds, GCC 8.3 or higher is needed.
|
|
|
|
|
|
2020-12-15 14:18:03 +00:00
|
|
|
For s390x architecture builds, GCC 7.1 or higher is needed (See gcc Bug 98269).
|
|
|
|
|
|
2023-04-12 13:37:49 +00:00
|
|
|
For AArch64 architecture builds with mathvec enabled, GCC 10 or higher is needed
|
|
|
|
|
due to dependency on arm_sve.h.
|
|
|
|
|
|
2016-10-07 07:56:46 +00:00
|
|
|
For multi-arch support it is recommended to use a GCC which has been built with
|
|
|
|
|
support for GNU indirect functions. This ensures that correct debugging
|
|
|
|
|
information is generated for functions selected by IFUNC resolvers. This
|
|
|
|
|
support can either be enabled by configuring GCC with
|
|
|
|
|
@samp{--enable-gnu-indirect-function}, or by enabling it by default by setting
|
|
|
|
|
@samp{default_gnu_indirect_function} variable for a particular architecture in
|
|
|
|
|
the GCC source file @file{gcc/config.gcc}.
|
|
|
|
|
|
2012-02-28 14:44:20 +00:00
|
|
|
You can use whatever compiler you like to compile programs that use
|
|
|
|
|
@theglibc{}.
|
1998-03-17 17:27:52 +00:00
|
|
|
|
2002-08-22 00:13:04 +00:00
|
|
|
Check the FAQ for any special compiler issues on particular platforms.
|
1998-11-30 16:42:19 +00:00
|
|
|
|
1998-03-17 17:27:52 +00:00
|
|
|
@item
|
2017-06-28 11:31:50 +00:00
|
|
|
GNU @code{binutils} 2.25 or later
|
1998-11-04 23:04:21 +00:00
|
|
|
|
2012-02-28 14:44:20 +00:00
|
|
|
You must use GNU @code{binutils} (as and ld) to build @theglibc{}.
|
2004-01-30 01:58:22 +00:00
|
|
|
No other assembler or linker has the necessary functionality at the
|
2024-01-30 23:13:43 +00:00
|
|
|
moment. As of release time, GNU @code{binutils} 2.42 is the newest
|
2015-02-06 03:56:00 +00:00
|
|
|
verified to work to build @theglibc{}.
|
1998-03-17 17:27:52 +00:00
|
|
|
|
2020-03-05 15:32:08 +00:00
|
|
|
For PowerPC 64-bits little-endian (powerpc64le), @command{objcopy} is required
|
|
|
|
|
to support @option{--update-section}. This option requires binutils 2.26 or
|
|
|
|
|
newer.
|
|
|
|
|
|
2017-11-20 20:46:17 +00:00
|
|
|
ARC architecture needs @code{binutils} 2.32 or higher for TLS related fixes.
|
|
|
|
|
|
1998-03-17 17:27:52 +00:00
|
|
|
@item
|
2014-12-11 17:59:45 +00:00
|
|
|
GNU @code{texinfo} 4.7 or later
|
1998-03-17 17:27:52 +00:00
|
|
|
|
|
|
|
|
To correctly translate and install the Texinfo documentation you need
|
|
|
|
|
this version of the @code{texinfo} package. Earlier versions do not
|
|
|
|
|
understand all the tags used in the document, and the installation
|
1998-11-09 18:21:06 +00:00
|
|
|
mechanism for the info files is not present or works differently.
|
2024-07-20 22:27:35 +00:00
|
|
|
As of release time, @code{texinfo} 7.1 is the newest verified to work
|
2015-02-06 03:56:00 +00:00
|
|
|
to build @theglibc{}.
|
1998-03-17 17:27:52 +00:00
|
|
|
|
|
|
|
|
@item
|
2013-06-17 16:54:51 +00:00
|
|
|
GNU @code{awk} 3.1.2, or higher
|
1998-11-04 23:04:21 +00:00
|
|
|
|
2013-06-17 16:54:51 +00:00
|
|
|
@code{awk} is used in several places to generate files.
|
|
|
|
|
Some @code{gawk} extensions are used, including the @code{asorti}
|
|
|
|
|
function, which was introduced in version 3.1.2 of @code{gawk}.
|
2024-07-20 22:27:35 +00:00
|
|
|
As of release time, @code{gawk} version 5.3.0 is the newest verified
|
2016-02-15 01:54:29 +00:00
|
|
|
to work to build @theglibc{}.
|
1998-11-04 23:04:21 +00:00
|
|
|
|
2017-11-30 21:21:15 +00:00
|
|
|
@item
|
|
|
|
|
GNU @code{bison} 2.7 or later
|
|
|
|
|
|
|
|
|
|
@code{bison} is used to generate the @code{yacc} parser code in the @file{intl}
|
2022-02-03 05:06:38 +00:00
|
|
|
subdirectory. As of release time, @code{bison} version 3.8.2 is the newest
|
2018-01-31 14:20:10 +00:00
|
|
|
verified to work to build @theglibc{}.
|
2017-11-30 21:21:15 +00:00
|
|
|
|
1998-11-04 23:04:21 +00:00
|
|
|
@item
|
|
|
|
|
Perl 5
|
|
|
|
|
|
2018-08-13 17:20:46 +00:00
|
|
|
Perl is not required, but if present it is used in some tests and the
|
2018-12-18 10:36:29 +00:00
|
|
|
@code{mtrace} program, to build the @glibcadj{} manual. As of release
|
2024-07-20 22:27:35 +00:00
|
|
|
time @code{perl} version 5.40.0 is the newest verified to work to
|
2018-12-18 10:36:29 +00:00
|
|
|
build @theglibc{}.
|
1998-03-17 17:27:52 +00:00
|
|
|
|
2000-02-26 01:21:37 +00:00
|
|
|
@item
|
|
|
|
|
GNU @code{sed} 3.02 or newer
|
|
|
|
|
|
2002-04-03 09:17:17 +00:00
|
|
|
@code{Sed} is used in several places to generate files. Most scripts work
|
2016-02-15 01:54:29 +00:00
|
|
|
with any version of @code{sed}. As of release time, @code{sed} version
|
2023-07-27 21:00:59 +00:00
|
|
|
4.9 is the newest verified to work to build @theglibc{}.
|
2000-02-26 01:21:37 +00:00
|
|
|
|
2018-08-13 17:20:46 +00:00
|
|
|
@item
|
2018-10-29 15:28:05 +00:00
|
|
|
Python 3.4 or later
|
2018-08-13 17:20:46 +00:00
|
|
|
|
2018-10-29 15:28:05 +00:00
|
|
|
Python is required to build @theglibc{}. As of release time, Python
|
2024-07-20 22:27:35 +00:00
|
|
|
3.12 is the newest verified to work for building and testing
|
2018-10-29 15:28:05 +00:00
|
|
|
@theglibc{}.
|
2018-08-13 17:20:46 +00:00
|
|
|
|
|
|
|
|
@item PExpect 4.0
|
|
|
|
|
|
|
|
|
|
The pretty printer tests drive GDB through test programs and compare
|
|
|
|
|
its output to the printers'. PExpect is used to capture the output of
|
|
|
|
|
GDB, and should be compatible with the Python version in your system.
|
2024-07-20 22:27:35 +00:00
|
|
|
As of release time PExpect 4.9.0 is the newest verified to work to test
|
2018-08-13 17:20:46 +00:00
|
|
|
the pretty printers.
|
|
|
|
|
|
|
|
|
|
@item
|
2023-08-25 12:15:29 +00:00
|
|
|
The Python @code{abnf} module.
|
|
|
|
|
|
|
|
|
|
This module is optional and used to verify some ABNF grammars in the
|
|
|
|
|
manual. Version 2.2.0 has been confirmed to work as expected. A
|
|
|
|
|
missing @code{abnf} module does not reduce the test coverage of the
|
|
|
|
|
library itself.
|
|
|
|
|
|
|
|
|
|
@item
|
2018-08-13 17:20:46 +00:00
|
|
|
GDB 7.8 or later with support for Python 2.7/3.4 or later
|
|
|
|
|
|
|
|
|
|
GDB itself needs to be configured with Python support in order to use
|
|
|
|
|
the pretty printers. Notice that your system having Python available
|
|
|
|
|
doesn't imply that GDB supports it, nor that your system's Python and
|
|
|
|
|
GDB's have the same version. As of release time GNU @code{debugger}
|
2024-07-20 22:27:35 +00:00
|
|
|
14.2 is the newest verified to work to test the pretty printers.
|
2018-08-13 17:20:46 +00:00
|
|
|
|
|
|
|
|
Unless Python, PExpect and GDB with Python support are present, the
|
|
|
|
|
printer tests will report themselves as @code{UNSUPPORTED}. Notice
|
|
|
|
|
that some of the printer tests require @theglibc{} to be compiled with
|
|
|
|
|
debugging symbols.
|
1998-03-17 17:27:52 +00:00
|
|
|
@end itemize
|
|
|
|
|
|
|
|
|
|
@noindent
|
2013-10-30 03:20:52 +00:00
|
|
|
If you change any of the @file{configure.ac} files you will also need
|
1998-03-17 17:27:52 +00:00
|
|
|
|
|
|
|
|
@itemize @bullet
|
|
|
|
|
@item
|
2024-06-11 21:34:54 +00:00
|
|
|
GNU @code{autoconf} 2.72 (exactly)
|
1998-03-17 17:27:52 +00:00
|
|
|
@end itemize
|
|
|
|
|
|
|
|
|
|
@noindent
|
|
|
|
|
and if you change any of the message translation files you will need
|
|
|
|
|
|
|
|
|
|
@itemize @bullet
|
|
|
|
|
@item
|
2001-04-19 20:15:22 +00:00
|
|
|
GNU @code{gettext} 0.10.36 or later
|
2018-07-31 20:37:07 +00:00
|
|
|
|
2024-07-20 22:27:35 +00:00
|
|
|
As of release time, GNU @code{gettext} version 0.22.4 is the newest
|
2018-07-31 20:37:07 +00:00
|
|
|
version verified to work to build @theglibc{}.
|
1998-03-17 17:27:52 +00:00
|
|
|
@end itemize
|
|
|
|
|
|
2014-12-11 17:27:34 +00:00
|
|
|
|
1998-03-17 17:27:52 +00:00
|
|
|
@noindent
|
|
|
|
|
You may also need these packages if you upgrade your source tree using
|
|
|
|
|
patches, although we try to avoid this.
|
|
|
|
|
|
1998-11-09 18:21:06 +00:00
|
|
|
@node Linux
|
2012-03-08 01:27:38 +00:00
|
|
|
@appendixsec Specific advice for @gnulinuxsystems{}
|
1998-11-09 18:21:06 +00:00
|
|
|
@cindex kernel header files
|
|
|
|
|
|
2012-03-08 01:27:38 +00:00
|
|
|
If you are installing @theglibc{} on @gnulinuxsystems{}, you need to have
|
Require Linux 3.2 except on x86 / x86_64, 3.2 headers everywhere.
In <https://sourceware.org/ml/libc-alpha/2016-01/msg00885.html> I
proposed a minimum Linux kernel version of 3.2 for glibc 2.24, since
Linux 2.6.32 has reached EOL.
In the discussion in February, some concerns were expressed about
compatibility with OpenVZ containers. It's not clear that these are
real issues, given OpenVZ backporting kernel features and faking the
kernel version for guest software, as discussed in
<https://sourceware.org/ml/libc-alpha/2016-02/msg00278.html>. It's
also not clear that supporting running GNU/Linux distributions from
late 2016 (at the earliest) on a kernel series from 2009 is a sensible
expectation. However, as an interim step, this patch increases the
requirement everywhere except x86 / x86_64 (since the controversy was
only about those architectures); the special caveats and settings can
easily be removed later when we're ready to increase the requirements
on x86 / x86_64 (and if someone would like to raise the issue on LWN
as suggested in the previous discussion, that would be welcome). 3.2
kernel headers are required everywhere by this patch.
(x32 already requires 3.4 or later, so is unaffected by this patch.)
As usual for such a change, this patch only changes the configure
scripts and associated documentation. The intent is to follow up with
removal of dead __LINUX_KERNEL_VERSION conditionals. Each __ASSUME_*
or other macro that becomes dead can then be removed independently.
Tested for x86_64 and x86.
* sysdeps/unix/sysv/linux/configure.ac (LIBC_LINUX_VERSION):
Define to 3.2.0.
(arch_minimum_kernel): Likewise.
* sysdeps/unix/sysv/linux/configure: Regenerated.
* sysdeps/unix/sysv/linux/i386/configure.ac (arch_minimum_kernel):
Define to 2.6.32.
* sysdeps/unix/sysv/linux/i386/configure: Regenerated.
* sysdeps/unix/sysv/linux/x86_64/64/configure.ac
(arch_minimum_kernel): Define to 2.6.32.
* sysdeps/unix/sysv/linux/x86_64/64/configure: Regenerated.
* README: Document Linux 3.2 requirement.
* manual/install.texi (Linux): Document Linux 3.2 headers
requirement.
* INSTALL: Regenerated.
2016-02-24 17:15:12 +00:00
|
|
|
the header files from a 3.2 or newer kernel around for reference.
|
2012-02-27 20:52:30 +00:00
|
|
|
These headers must be installed using @samp{make headers_install}; the
|
|
|
|
|
headers present in the kernel source directory are not suitable for
|
2012-02-28 14:44:20 +00:00
|
|
|
direct use by @theglibc{}. You do not need to use that kernel, just have
|
|
|
|
|
its headers installed where @theglibc{} can access them, referred to here as
|
2012-02-27 20:52:30 +00:00
|
|
|
@var{install-directory}. The easiest way to do this is to unpack it
|
|
|
|
|
in a directory such as @file{/usr/src/linux-@var{version}}. In that
|
|
|
|
|
directory, run @samp{make headers_install
|
2012-02-28 14:44:20 +00:00
|
|
|
INSTALL_HDR_PATH=@var{install-directory}}. Finally, configure @theglibc{}
|
2012-02-27 20:52:30 +00:00
|
|
|
with the option @samp{--with-headers=@var{install-directory}/include}.
|
|
|
|
|
Use the most recent kernel you can get your hands on. (If you are
|
2012-02-28 14:44:20 +00:00
|
|
|
cross-compiling @theglibc{}, you need to specify
|
2012-02-27 20:52:30 +00:00
|
|
|
@samp{ARCH=@var{architecture}} in the @samp{make headers_install}
|
|
|
|
|
command, where @var{architecture} is the architecture name used by the
|
|
|
|
|
Linux kernel, such as @samp{x86} or @samp{powerpc}.)
|
2003-01-15 07:15:24 +00:00
|
|
|
|
2012-02-28 14:44:20 +00:00
|
|
|
After installing @theglibc{}, you may need to remove or rename
|
2012-02-27 20:52:30 +00:00
|
|
|
directories such as @file{/usr/include/linux} and
|
|
|
|
|
@file{/usr/include/asm}, and replace them with copies of directories
|
|
|
|
|
such as @file{linux} and @file{asm} from
|
|
|
|
|
@file{@var{install-directory}/include}. All directories present in
|
|
|
|
|
@file{@var{install-directory}/include} should be copied, except that
|
2012-02-28 14:44:20 +00:00
|
|
|
@theglibc{} provides its own version of @file{/usr/include/scsi}; the
|
2012-02-27 20:52:30 +00:00
|
|
|
files provided by the kernel should be copied without replacing those
|
2012-02-28 14:44:20 +00:00
|
|
|
provided by @theglibc{}. The @file{linux}, @file{asm} and
|
2012-02-27 20:52:30 +00:00
|
|
|
@file{asm-generic} directories are required to compile programs using
|
2012-02-28 14:44:20 +00:00
|
|
|
@theglibc{}; the other directories describe interfaces to the kernel but
|
2012-02-27 20:52:30 +00:00
|
|
|
are not required if not compiling programs using those interfaces.
|
|
|
|
|
You do not need to copy kernel headers if you did not specify an
|
|
|
|
|
alternate kernel header source using @samp{--with-headers}.
|
1998-11-09 18:21:06 +00:00
|
|
|
|
2012-03-08 01:27:38 +00:00
|
|
|
The Filesystem Hierarchy Standard for @gnulinuxsystems{} expects some
|
|
|
|
|
components of the @glibcadj{} installation to be in
|
1998-11-09 18:21:06 +00:00
|
|
|
@file{/lib} and some in @file{/usr/lib}. This is handled automatically
|
2012-02-28 14:44:20 +00:00
|
|
|
if you configure @theglibc{} with @samp{--prefix=/usr}. If you set some other
|
1998-11-09 18:21:06 +00:00
|
|
|
prefix or allow it to default to @file{/usr/local}, then all the
|
|
|
|
|
components are installed there.
|
|
|
|
|
|
2024-07-20 22:27:35 +00:00
|
|
|
As of release time, Linux version 6.6 is the newest stable version verified
|
2022-02-03 05:06:38 +00:00
|
|
|
to work to build @theglibc{}.
|
|
|
|
|
|
1998-03-17 17:27:52 +00:00
|
|
|
@node Reporting Bugs
|
|
|
|
|
@appendixsec Reporting Bugs
|
|
|
|
|
@cindex reporting bugs
|
|
|
|
|
@cindex bugs, reporting
|
|
|
|
|
|
2012-02-28 14:44:20 +00:00
|
|
|
There are probably bugs in @theglibc{}. There are certainly
|
1998-03-17 17:27:52 +00:00
|
|
|
errors and omissions in this manual. If you report them, they will get
|
|
|
|
|
fixed. If you don't, no one will ever know about them and they will
|
|
|
|
|
remain unfixed for all eternity, if not longer.
|
|
|
|
|
|
1999-08-27 19:06:58 +00:00
|
|
|
It is a good idea to verify that the problem has not already been
|
|
|
|
|
reported. Bugs are documented in two places: The file @file{BUGS}
|
2012-11-09 22:13:45 +00:00
|
|
|
describes a number of well known bugs and the central @glibcadj{}
|
|
|
|
|
bug tracking system has a
|
1999-04-08 03:03:02 +00:00
|
|
|
WWW interface at
|
2017-11-16 06:19:26 +00:00
|
|
|
@url{https://sourceware.org/bugzilla/}. The WWW
|
2002-04-03 09:17:17 +00:00
|
|
|
interface gives you access to open and closed reports. A closed report
|
|
|
|
|
normally includes a patch or a hint on solving the problem.
|
1999-04-08 03:03:02 +00:00
|
|
|
|
2002-04-03 09:17:17 +00:00
|
|
|
To report a bug, first you must find it. With any luck, this will be the
|
1998-03-17 17:27:52 +00:00
|
|
|
hard part. Once you've found a bug, make sure it's really a bug. A
|
2012-02-28 14:44:20 +00:00
|
|
|
good way to do this is to see if @theglibc{} behaves the same way
|
1998-03-17 17:27:52 +00:00
|
|
|
some other C library does. If so, probably you are wrong and the
|
|
|
|
|
libraries are right (but not necessarily). If not, one of the libraries
|
2012-02-28 14:44:20 +00:00
|
|
|
is probably wrong. It might not be @theglibc{}. Many historical
|
1998-11-09 18:21:06 +00:00
|
|
|
Unix C libraries permit things that we don't, such as closing a file
|
|
|
|
|
twice.
|
|
|
|
|
|
2012-02-28 14:44:20 +00:00
|
|
|
If you think you have found some way in which @theglibc{} does not
|
1998-11-09 18:21:06 +00:00
|
|
|
conform to the ISO and POSIX standards (@pxref{Standards and
|
|
|
|
|
Portability}), that is definitely a bug. Report it!
|
1998-03-17 17:27:52 +00:00
|
|
|
|
|
|
|
|
Once you're sure you've found a bug, try to narrow it down to the
|
|
|
|
|
smallest test case that reproduces the problem. In the case of a C
|
|
|
|
|
library, you really only need to narrow it down to one library
|
|
|
|
|
function call, if possible. This should not be too difficult.
|
|
|
|
|
|
|
|
|
|
The final step when you have a simple test case is to report the bug.
|
2012-11-09 22:13:45 +00:00
|
|
|
Do this at @value{REPORT_BUGS_TO}.
|
1998-03-17 17:27:52 +00:00
|
|
|
|
|
|
|
|
If you are not sure how a function should behave, and this manual
|
|
|
|
|
doesn't tell you, that's a bug in the manual. Report that too! If the
|
|
|
|
|
function's behavior disagrees with the manual, then either the library
|
|
|
|
|
or the manual has a bug, so report the disagreement. If you find any
|
2004-05-17 18:59:35 +00:00
|
|
|
errors or omissions in this manual, please report them to the
|
|
|
|
|
bug database. If you refer to specific
|
1999-08-27 19:06:58 +00:00
|
|
|
sections of the manual, please include the section names for easier
|
|
|
|
|
identification.
|
