%general-entities; ]> When building packages there are several assumptions made within the instructions: Several of the packages are patched before compilation, but only when the patch is needed to circumvent a problem. A patch is often needed in both this and the next chapter, but sometimes in only one or the other. Therefore, do not be concerned if instructions for a downloaded patch seem to be missing. Warning messages about offset or fuzz may also be encountered when applying a patch. Do not worry about these warnings, as the patch was still successfully applied. During the compilation of most packages, there will be several warnings that scroll by on the screen. These are normal and can safely be ignored. These warnings are as they appear—warnings about deprecated, but not invalid, use of the C or C++ syntax. C standards change fairly often, and some packages still use the older standard. This is not a problem, but does prompt the warning. After installing each package, delete its source and build directories, unless specifically instructed otherwise. Deleting the sources prevents mis-configuration when the same package is reinstalled later. Check one last time that the LFS environment variable is set up properly: echo $LFS Make sure the output shows the path to the LFS partition's mount point, which is /mnt/lfs, using our example. Finally, two last important items must be emphasized: The build instructions assume that the bash shell is in use. Before issuing the build instructions for a package, the package should be unpacked as user lfs, and a cd into the created directory should be performed.