diff --git a/chapter01/changelog.xml b/chapter01/changelog.xml index d0cf45003..69860723f 100644 --- a/chapter01/changelog.xml +++ b/chapter01/changelog.xml @@ -40,7 +40,7 @@ appropriate for the entry or if needed the entire day's listitem. --> - + 2024-08-23 @@ -50,7 +50,7 @@ - + 2024-08-23 @@ -174,7 +174,7 @@ [bdubbs] - Update to setuptools-72.1.0. Fixes #5531. - + [bdubbs] - Update to sysklogd-2.6.1. Fixes #5522. @@ -231,7 +231,7 @@ - + 2024-07-01 @@ -260,7 +260,7 @@ [bdubbs] - Update to linux-6.9.7. Fixes #5508. - + [bdubbs] - Update to sysklogd-2.5.2. Fixes #5509. diff --git a/chapter08/gcc.xml b/chapter08/gcc.xml index d50fbaa5e..e79828730 100644 --- a/chapter08/gcc.xml +++ b/chapter08/gcc.xml @@ -135,10 +135,16 @@ cd build command below, where x is the number of CPU cores on your system. - One set of tests in the GCC test suite is known to exhaust the default - stack, so increase the stack size prior to running the tests: + GCC may need more stack space compiling some extremely complex + code patterns. As a precaution for the host distros with a tight stack + limit, explicitly set the stack size hard limit to infinite. + On most host distros (and the final LFS system) the hard limit is + infinite by default, but there is no harm done by setting it explicitly. + It's not necessary to change the stack size soft limit because GCC will + automatically set it to an appropriate value, as long as the value does + not exceed the hard limit: -ulimit -s 32768 +ulimit -s -H unlimited Now remove/fix several known test failures: