2. FAQ
3. Search

Filters

• Untranslated strings • state:empty
• Unfinished strings • state:<translated
• Translated strings • state:>=translated
• Strings marked for edit • state:needs-editing
• Strings with suggestions • has:suggestion
• Strings with variants • has:variant
• Strings with screenshots • has:screenshot
• Strings with labels • has:label
• Strings with context • has:context
• Unfinished strings without suggestions • state:<translated AND NOT has:suggestion
• Strings with comments • has:comment
• Strings with any failing checks • has:check
• Approved strings • state:approved
• Strings waiting for review • state:translated

state:empty

Position and priority

• Position and priority
• Position
• Priority
• Labels
• Source string
• Target string
• String age
• Last updated
• Number of words
• Number of comments
• Number of failing checks
• Key
• String location

	Translation	Source string	Target string
	FAQ/FAQ — French	You should understand how "conditions" like [ ... ] work in bash: "[" is a command and "]" should be its last parameter. So there must be a whitespace before "]", or the execution of "[" will fail.
	FAQ/FAQ — French	And, please note that different packages have different versioning schemes. For example, for many packages versions with an odd minor version ("y" in "x.y.z") are development snapshots and some other packages use patch levels ("z" in "x.y.z") greater than or equal to 90 for pre-releases. LFS/BLFS won't use development snapshots or pre-releases unless there is a good reason.
	FAQ/FAQ — French	Please read <a href="../lfs/view/development/chapter08/pkgmgt.html">the section named "Upgrade Issues"</a> carefully before upgrading any package.
	FAQ/FAQ — French	<a href="#include-next-not-found">"fatal error: foo.h: No such file or directories" on include_next directives in C++ standard headers</a>
	FAQ/FAQ — French	<a href="#oom-kill">"fatal error: Killed signal terminated program cc1plus"</a>
	FAQ/FAQ — French	Some package installs libraries into <code>/usr/lib64</code>
	FAQ/FAQ — French	Some packages (notably, all packages using meson building system) will use <code>/usr/lib64</code> as the default library install directory <b>if this directory exists</b>. On a BLFS system this directory should not exist. Try to figure out why it has been created and then remove it. You may need to reinstall some packages and ensure their libraries are in the correct location, which is <code>/usr/lib</code>.
	FAQ/FAQ — French	Please follow the book carefully when you build and install cmake: omitting the <code>sed</code> command in the instruction can cause cmake to install libraries into <code>/usr/lib64</code>.
	FAQ/FAQ — French	A library in <code>/usr/lib64</code> on BLFS won't work because <code>ld-linux-x86-64.so.2</code> from LFS does not search <code>/usr/lib64</code>. If you are installing some packages beyond the scope of BLFS, you may need to find how to ensure installing the libraries into <code>/usr/lib</code> instead of <code>/usr/lib64</code> yourself.
	FAQ/FAQ — French	"fatal error: foo.h: No such file or directories" on include_next directives in C++ standard headers
	FAQ/FAQ — French	Please make sure your <code>CPLUS_INCLUDE_PATH</code> environment variable does not contain <code>/usr/include</code>.
	FAQ/FAQ — French	Especially, don't use the commands for Xorg installation outside of <code>/usr</code> if you are installing Xorg into <code>/usr</code>.
	FAQ/FAQ — French	"fatal error: Killed signal terminated program cc1plus"
	FAQ/FAQ — French	If it's possible, you can solve the problem by adding more RAM into your system. Otherwise, run make or ninja with "-j N", where N should be replaced with a relatively small positive integer. You can try the value of N from the number of your CPU cores, down to 1.
	FAQ/FAQ — French	If this issue still lingers with N = 1, you should really add more RAM. You may work around it by adding more swap, but swapping can make the building process slower.
	FAQ/FAQ — French	It's because libbfd.la refers to the non-exist libiberty. libbfd.la should be removed in LFS ("Cleaning Up" section) as we consider all .la files in LFS unneeded and harmful.
	FAQ/FAQ — French	Please do not skip any section building LFS. You may skip some instruction only if the book explicitly says it's optional.
	FAQ/FAQ — French	<a id="lfsfaq"/>
	FAQ/FAQ — French	<a href="#rebuild-ch8">Can I skip a package in Chapter 8 since it's already built in Chapter 6 or 7, and it's functioning properly?</a>
	FAQ/FAQ — French	<a href="#get-rid-of-lib64">Can I modify GCC code and get rid of /lib64?</a>
	FAQ/FAQ — French	<a href="#config-ice">Why does GCC reports "Internal Compiler Error" for a "hello world" program?</a>
	FAQ/FAQ — French	<a href="#m4-mb-len-max-wrong">M4: Assumed value of MB_LEN_MAX wrong</a>
	FAQ/FAQ — French	<a href="#systemd-user-credentials-esrch">Systemd: systemd-networkd.service: Failed to determine user credentials: No such process</a>
	FAQ/FAQ — French	<a href="#irq-nobody-cared">IRQ 9: nobody cared (try booting with the "irqpoll" option)</a>
	FAQ/FAQ — French	<a href="#lfs-very-slow">LFS system is much slower than the host distro (or another distro)</a>
	FAQ/FAQ — French	How do I boot LFS with UEFI?
	FAQ/FAQ — French	GRUB can be built for UEFI, but doing so needs several packages beyond the scope of LFS. You can consult <a href="/blfs/view/svn/postlfs/grub-efi.html">the BLFS page for it</a>.
	FAQ/FAQ — French	Can I skip a package in Chapter 8 since it's already built in Chapter 6 or 7, and it's functioning properly?
	FAQ/FAQ — French	Long answer: we want LFS to be "settled down": if some package is rebuilt in the LFS system, the result (libraries and binaries) should be same as the result at the end of the LFS book. In Chapter 6 the tools are cross compiled, where many tests in the <code>configure</code> script can't be done. The "guessed" result will be used, unnecessary workarounds are enabled, or optional features are disabled. The tools in Chapter 7 are built for resolving circular dependencies: many of their optional features depend on packages not built yet and have to be disabled. So rebuilding them in Chapter 8 is necessary.
	FAQ/FAQ — French	On the other hand, if you are building Linux for some really tiny platform where you can't build packages in a reasonable time (for example, a 16 MHz ARM), you can cross compile everything in Chapter 6 since Chapter 7 and 8 are not applicable. Or, you can do Chapter 7 and 8 with an emulator like <a href="/blfs/view/stable/postlfs/qemu.html">QEMU</a>.
	FAQ/FAQ — French	Can I modify GCC code and get rid of /lib64?
	FAQ/FAQ — French	Long answer: LSB mandates the ELF loader to be at /lib64/ld-linux-x86-64.so.2 on x86-64.
	FAQ/FAQ — French	Even longer answer: when the kernel is told to execute a dynamic linked ELF executable, it reads the path to the ELF loader hard-coded in the ELF executable, which is /lib64/ld-linux-x86-64.so.2. So, if it does not exist, LFS won't be able to run any dynamic linked executable compiled elsewhere. For example, executables from commercial software packages (MATLAB or COMSOL) or binaries downloaded from GitHub release page will not run.
	FAQ/FAQ — French	Most relatively recent distributions should be fine. You could consult <a href="/lfs/view/stable/chapter02/hostreqs.html">the Host System Requirements page</a>.
	FAQ/FAQ — French	Make sure you have installed and/or updated the development packages. (Look for ones starting in "gcc", "glibc", or "libstdc++" or ending in "-dev" or "-devel".)
	FAQ/FAQ — French	If you want to use LFS as your main system and you wish to install it without first installing a distribution, It is also possible to use a live image on dvd or usb stick. All major distributions provide one.
	FAQ/FAQ — French	If you can determine that some warning indicates a real bug in the software, report to the maintainer of it.
	FAQ/FAQ — French	For ARM, consult LFS Fork for ARM (64-bit or 32-bit) (<a href='https://clfs.org/~kb0iic/lfs-sysv'>SysV</a> and <a href='https://clfs.org/~kb0iic/lfs-systemd'>Systemd</a>), maintained by William Harrington; and another LFS ARM64 Branch (64-bit only, <a href='https://www.linuxfromscratch.org/~xry111/lfs/view/arm64-systemd/'>Systemd</a> and <a href='https://www.linuxfromscratch.org/~xry111/lfs/view/arm64/'>SysV [NOT TESTED!]</a>), maintained by Xi Ruoyao.
	FAQ/FAQ — French	The resources provided above are quite outdated. You can modify the LFS building process after LFS 10.0 (developed by Pierre Labestie) to cross compile LFS: set <span>$LFS_TGT</span> to the triplet of your target platform, and build cross toolchain in Chapter 5 and temporary tools in Chapter 6 as normal. At the end of Chapter 6, build a kernel and a bootloader for the target. Then copy the temporary system to the target platform, boot it, and continue the building from Chapter 7. Read clfs-ng branch (<a href='https://www.linuxfromscratch.org/~xry111/lfs/view/clfs-ng/'>SysV</a> and <a href='https://www.linuxfromscratch.org/~xry111/lfs/view/clfs-ng-systemd/'>Systemd</a>) for details.
	FAQ/FAQ — French	configure output shows errors, isn't "gcc -V" wrong?
	FAQ/FAQ — French	To determine what is present on the system, the configure scripts try various commands with various command line options. They then take actions depending on the exit code of the commands. Some of those commands may write error messages, and this is what you see, for example with "gcc -V". But the configure script itself has not failed.
	FAQ/FAQ — French	Why does GCC reports "Internal Compiler Error" for a "hello world" program?
	FAQ/FAQ — French	CPU overheating is another common hardware problem. Ensure the cooler is properly installed with thermal paste applied. And, some coolers (especially all-in-one liquid coolers) cannot be configured via BIOS and they need special software (for example, <a href='https://github.com/liquidctl/liquidctl'>liquidctl</a> to set the parameters correctly. If such a cooler is not properly configured, it can run in a lower speed (or does not run at all). If the cooler is already running at full speed but the CPU still overheats, either upgrade the cooler, or downclock the CPU via BIOS.
	FAQ/FAQ — French	If both bad memory and CPU overheating can be ruled out, see the long answer.
	FAQ/FAQ — French	Check if the symlink /lib64/ld-linux-x86-64.so.2 is broken. For LFS 9.1 or older, it may indicate a typo in GCC Pass 2.
	FAQ/FAQ — French	M4: Assumed value of MB_LEN_MAX wrong
	FAQ/FAQ — French	This error message usually indicates that <code>limits.h</code> provided by GCC isn't including <code>limits.h</code> from Glibc as it should be. There are two commands as a workaround for <code>limits.h</code> in Chapter 5, one in GCC Pass 1 and another in Glibc. Forgetting any of them will lead to this issue. You can rerun the forgotten commands (untar GCC tarball if necessary) and retry to build M4. Note that if you forgot the command in GCC Pass 1, you'll have to rerun both of these two workarounds, as the workaround in Glibc copies from the file created in the workaround in GCC Pass 1.
	FAQ/FAQ — French	Systemd: systemd-networkd.service: Failed to determine user credentials: No such process
	FAQ/FAQ — French	It's likely because <code>/etc/passwd</code> for sysv revision is misused in systemd-based system. "No such process" is just the "standard" error message for <code>ESRCH</code>, it's not very helpful for diagnosis of this issue.
	FAQ/FAQ — French	And, udev may rename your network devices. For example, eth0 may be renamed to enp4s0. You can run <code>ip link</code> command after booting the LFS system, and examine the output to know the name of your network devices.
	FAQ/FAQ — French	irq 9: nobody cared (try booting with the "irqpoll" option)
	FAQ/FAQ — French	It may be a bug in the firmware (BIOS) or the drivers in kernel. Some hardware vendors tend to use Windows-specific hacks in their BIOS, which is misinterpreted by Linux kernel and causing this kind of issue.
	FAQ/FAQ — French	If you see message like this but your system functions normally, you can ignore it. If the system malfunctions, you can try the combinations of several kernel options to workaround: <code>irqpoll</code>, <code>noapic</code>, <code>pci=nocrs</code>, and <code>i8042.nopnp=1</code>.
	FAQ/FAQ — French	And, you can try <a href="https://wiki.debian.org/OverridingDSDT">ACPI DSDT override</a> if you really understand it.
	FAQ/FAQ — French	You can always report this kind of issue to <a href="https://bugzilla.kernel.org">Kernel bug tracker</a>, no matter if it's a BIOS bug. The kernel developers want to make Linux runable even if the BIOS has this kind of bug.
	FAQ/FAQ — French	LFS system is much slower than the host distro (or another distro)
	FAQ/FAQ — French	If the LFS system is slower than another distro but not much slower, it's normal. We focus on building a Linux system from source code and we do nothing to tweak the system for marginal performance improvements. The other distros may enable additional compiler optimizations, tune kernel options (via sysctl), or use other approaches to squeeze more performance out. And, LFS uses a latest GCC release which is likely slower than an old GCC release. A new GCC release often attempts to optimize the target code more heavily (these optimizations will slow down the compiliation, but hopefully make the compiled program faster). So LFS will take more time building a large package (like Linux kernel).
	FAQ/FAQ — French	But, if the LFS system is <b>very</b> slow (for example, takes 5 hours to build a kernel while the host distro needs only one hour to build the same kernel with exactly same configuration), it likely indicates a CPU dynamic frequency scaling issue. You can monitor the value of "cpu MHz" in <code>/proc/cpuinfo</code> to see if your CPU is running at a reasonable frequency while a workload (like, building the kernel) is running on the CPU.
	FAQ/FAQ — French	If your CPU is running at a much lower frequency than expected (an Intel Core i3 building the kernel but running at only 800 MHz is definitely too slow), try to adjust the setting of "Default CPUFreq governor" in the kernel configuration and rebuild the kernel. The ideal setting should limit the CPU at a low frequency when the system is idle, but boost it to the maximum performance while a workload is running.
	FAQ/FAQ — French	Note that a governor may behave differently on different CPUs. For example, the "powersave" governor may work fine for one CPU model, but lock another CPU at 800 MHz no matter if there is a workload running. If you can't (or don't want to spend too much time to) find an ideal setting, use the "performance" governor.