AuroraMiddleware/glibc
1
0
Fork 0
mirror of https://sourceware.org/git/glibc.git synced 2024-11-25 14:30:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

Document general use of test-wrapper and test-wrapper-env.

Browse Source
This commit is contained in:
Joseph Myers 2012-10-31 20:43:54 +00:00
parent 84097ebac3
commit 0eb6951257
3 changed files with 26 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
ChangeLog
View File

@ -1,5 +1,9 @@
2012-10-31 Joseph Myers <joseph@codesourcery.com>
* manual/install.texi (Configuring and compiling): Document
general use of test-wrapper and test-wrapper-env.
* INSTALL: Regenerated.
* sysdeps/ieee754/dbl-64/s_fma.c: Include <tininess.h>.
(__fma): Do not extract and scale down low bits on after-rounding
systems when result rounded to normal precision would have normal

11
INSTALL
View File

@ -204,6 +204,17 @@ HOSTNAME is the host name of a system that can run the newly built
binaries of the GNU C Library. The source and build directories must
be visible at the same locations on both the build system and HOSTNAME.
In general, when testing the GNU C Library, `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
working directory, all environment variables set as part of testing and
the standard input, output and error file descriptors. If
`TEST-WRAPPER env' will not work to run a program with environment
variables set, then `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 `VAR=VALUE' before the
name of the program to be run.
Installing the C Library
========================

11
manual/install.texi
View File

@ -233,6 +233,17 @@ 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}.
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
working directory, all environment variables set as part of testing
and the standard input, output and error file 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.
@node Running make install
@appendixsec Installing the C Library