From 75a38113a7931e9880b148abab881578fc416ea8 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Sun, 5 Feb 2023 12:49:57 -0800 Subject: doc: update README-hacking * README-hacking: Update for current bootstrap. --- README-hacking | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/README-hacking b/README-hacking index 3d95d10..a8a0be6 100644 --- a/README-hacking +++ b/README-hacking @@ -16,7 +16,7 @@ Specific development tools and versions will be checked for and listed by the bootstrap script. See README-prereq for specific notes on obtaining these prerequisite tools. -Valgrind is also highly recommended, if +Valgrind is also highly recommended, if Valgrind supports your architecture. See also README-valgrind (if present). @@ -46,13 +46,13 @@ time and file system space requirements: $ export GNULIB_SRCDIR=/path/to/gnulib The next step is to get and check other files needed to build, -which are extracted from other source packages: +which are extracted from other source packages [1]: $ ./bootstrap And there you are! Just - $ ./configure --quiet #[--disable-gcc-warnings] [*] + $ ./configure --quiet #[--disable-gcc-warnings] [2] $ make $ make check @@ -65,7 +65,13 @@ should output no difference. Enjoy! -[*] By default GCC warnings are enabled when building from Git. +[1] You can also bootstrap in two phases: first, './bootstrap --pull' +fetches auxiliary files from the network, and then './bootstrap --gen' +generates files by using local tools without accessing the net. +Although './bootstrap' by default does both phases, auditable builds +can do them separately. + +[2] By default GCC warnings are enabled when building from Git. If you get warnings with recent GCC and Glibc with default configure-time options, please report the warnings to the bug reporting address of this package instead of to bug-gnulib, -- cgit v1.2.1