mirror of
https://git.linuxfromscratch.org/lfs.git
synced 2025-03-06 14:24:48 +00:00
I've had doubts on this "ulimit -s 32768" command for years. After reading GCC code (libiberty/stack-limit.c) I'm pretty sure this command is not doing what we expected. In a typical Linux distro, the default "soft" stack limit is 8 MiB and the default "hard" stack limit is infinite. And GCC will automatically increase the soft limit to 64 MiB if the original soft limit is smaller than 64 MiB, and the hard limit is at least 64 MiB. So with a typical default configuration, the real stack limit of GCC is 64 MiB. But our "ulimit -s 32768" command sets both the soft limit and the hard limit to 32 MiB. Thus we are actually *decreasing* the real stack limit. Fortunately this has not caused any test failures, but it's just wrong (contradicting with the explanation of the command). Thus just raise the hard limit to infinite in case the host distro uses a not so typical configuration where the hard limit is tight, and let GCC to set up the soft limit to the expected value on its own. It's more future-proof than "ulimit -s 65536" in case GCC changes the expected stack limit in the future. It should be safe to make the change in freeze because in jhalfs it only affects the test suite, and even in a manual build the user can skip this command if not running the GCC test suite. |
||
---|---|---|
appendices | ||
bootscripts | ||
chapter01 | ||
chapter02 | ||
chapter03 | ||
chapter04 | ||
chapter05 | ||
chapter06 | ||
chapter07 | ||
chapter08 | ||
chapter09 | ||
chapter10 | ||
chapter11 | ||
images | ||
part3intro | ||
prologue | ||
stylesheets | ||
udev-lfs | ||
.gitignore | ||
aux-file-data.sh | ||
gen-changelog.py | ||
general.ent | ||
git-version.sh | ||
index.xml | ||
INSTALL | ||
lfs-latest-git.php | ||
lfs-latest.php | ||
make-aux-files.sh | ||
Makefile | ||
obfuscate.sh | ||
packages.ent | ||
patches.ent | ||
pdf-fixups.sh | ||
process-scripts.sh | ||
README | ||
tidy.conf |
LFS Book README This document is meant to instruct the user on how to convert the book's XML source to other formats (e.g. HTML, PDF, PS and TXT). First, if you have not already done so, please read the INSTALL file for instructions on how to install the required software. If you have already completed the steps outlined in the INSTALL file, then continue reading for examples how to convert these files into various other formats. In all examples, setting the parameter REV=systemd is needed to build the systemd version of the book. XML to XHTML: ------------- make BASEDIR=/path/to/output/location XML to single file XHTML (nochunks): ------------------------------------ make BASEDIR=/path/to/output/location nochunks XML to TXT ---------- Follow the instructions for nochunks and then run: lynx -dump /path/to/nochunks >/path/to/output XML to PDF: ----------- make BASEDIR=/path/to/output/location pdf