X-Git-Url: http://git.ipfire.org/?a=blobdiff_plain;f=INSTALL;h=392537cc5c2b099e030ea62582f82c45dc7ec28b;hb=4052fa22f69c0964bb42c0f13daa791617253de5;hp=268b7d63fab31ff5276e0d0b13bd1f1f8dca4ddb;hpb=053c52b17739a584ee73d336e547b15abcdabd49;p=thirdparty%2Fglibc.git diff --git a/INSTALL b/INSTALL index 268b7d63fab..392537cc5c2 100644 --- a/INSTALL +++ b/INSTALL @@ -176,10 +176,10 @@ if 'CFLAGS' is specified it must enable optimization. For example: protection. '--enable-bind-now' - Disable lazy binding for installed shared objects. 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. + 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. '--enable-pt_chown' The file 'pt_chown' is a helper binary for 'grantpt' (*note @@ -459,19 +459,14 @@ build the GNU C Library: As of relase time, GNU 'make' 4.2.1 is the newest verified to work to build the GNU C Library. - * GCC 4.9 or newer + * GCC 6.2 or newer - GCC 4.9 or higher is required. In general it is recommended to use + GCC 6.2 or higher is required. In general it is recommended to use the newest version of the compiler that is known to work for building the GNU C Library, as newer compilers usually produce - better code. As of release time, GCC 8.1.1 is the newest compiler + better code. As of release time, GCC 9.1.1 is the newest compiler verified to work to build the GNU C Library. - For PowerPC 64-bits little-endian (powerpc64le), GCC 6.2 or higher - is required. This compiler version is the first to provide the - features required for building the GNU C Library with support for - '_Float128'. - 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 @@ -500,7 +495,7 @@ build the GNU C Library: need this version of the 'texinfo' package. Earlier versions do not understand all the tags used in the document, and the installation mechanism for the info files is not present or works - differently. As of release time, 'texinfo' 6.5 is the newest + differently. As of release time, 'texinfo' 6.6 is the newest verified to work to build the GNU C Library. * GNU 'awk' 3.1.2, or higher @@ -514,14 +509,14 @@ build the GNU C Library: * GNU 'bison' 2.7 or later 'bison' is used to generate the 'yacc' parser code in the 'intl' - subdirectory. As of release time, 'bison' version 3.0.4 is the + subdirectory. As of release time, 'bison' version 3.0.5 is the newest verified to work to build the GNU C Library. * Perl 5 Perl is not required, but if present it is used in some tests and the 'mtrace' program, to build the GNU C Library manual. As of - release time 'perl' version 5.28.0 is the newest verified to work + release time 'perl' version 5.28.2 is the newest verified to work to build the GNU C Library. * GNU 'sed' 3.02 or newer @@ -533,8 +528,8 @@ build the GNU C Library: * Python 3.4 or later Python is required to build the GNU C Library. As of release time, - Python 3.6 is the newest verified to work for building and testing - the GNU C Library. + Python 3.7.4 is the newest verified to work for building and + testing the GNU C Library. * PExpect 4.0 @@ -550,8 +545,8 @@ build the GNU C Library: 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 'debugger' 8.0.1 is the newest verified to work to test - the pretty printers. + time GNU 'debugger' 8.3 is the newest verified to work to test the + pretty printers. Unless Python, PExpect and GDB with Python support are present, the printer tests will report themselves as 'UNSUPPORTED'. Notice that @@ -648,7 +643,7 @@ 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. -Do this at . +Do this at . 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