diff options
Diffstat (limited to 'chapter05/whystatic.xml')
| -rw-r--r-- | chapter05/whystatic.xml | 25 |
1 files changed, 8 insertions, 17 deletions
diff --git a/chapter05/whystatic.xml b/chapter05/whystatic.xml index 59b221e55..86a550154 100644 --- a/chapter05/whystatic.xml +++ b/chapter05/whystatic.xml @@ -42,23 +42,14 @@ of the improved function.</para> memory space, disk space, and recompile time.</para> <para>But if dynamic linking saves so much space, why then are we linking -all programs in this chapter statically? The reason is that we won't be -compiling a temporary <filename>glibc</filename> here. And we avoid doing this -simply to save some time -- around 14 SBUs. Another reason is that the -Glibc version on the LFS system might not be compatible with the Glibc on -the host system. Applications compiled against your host system's Glibc -version may not run properly (or at all) on the LFS system.</para> - -<para>This means that the tools compiled in this chapter will have to be -self-contained, because when later on we chroot to the LFS partition the -GNU library won't be available. That is why we use the -<userinput>-static</userinput>, <userinput>--enable-static-link</userinput>, -and <userinput>--disable-shared</userinput> flags throughout this chapter, to -ensure that all executables are statically linked. When we come to the next -chapter, almost the first thing we do is build <filename>glibc</filename>, the -main set of system libraries. Once this is done, we can link all other programs -dynamically (including the ones installed statically in this chapter) and -take advantage of the space saving opportunities.</para> +the first two packages in this chapter statically? The reason is to make them +independent from the libraries on your host system. And the point in that is +that, if you are pressed for time, you could skip the second passes over GCC +and Binutils, and just use the static versions to compile the rest of this +chapter and the first few packages in the next. As in the next chapter we +will be chrooted to the LFS partition and your host system's Glibc won't be +available, the programs from GCC and Binutils will need to be self-contained, +that is statically linked.</para> </sect1> |