On Sun, 2020-06-28 at 15:43 +0200, Frans de Boer wrote: > On 28-06-2020 15:16, Pierre Labastie wrote: > > On Sun, 2020-06-28 at 13:42 +0200, Frans de Boer wrote: > > > LS, > > > > > > Currently, the previous chapter 5 has been split into 3 separate > > > chapters. It is obvious why the new chapter 7 exists. > > > However, chapter 5 and 6 are a bit puzzling. There are no extra > > > actions > > > between chapter 6 and 5, in fact one could argue that 5 and 6 can > > > be > > > fussed together. > > > > > > The only reason I can think of to explain the separation between > > > chapter > > > 5 and 6, is that chapter 5 provides the basic building blocks to > > > compile > > > the remaining of chapter 6. Which can be reused if (some of) > > > chapter > > > 6 > > > needs a rebuild. After all, the next step is a different > > > architecture > > > where this approach can be used. > > > That said, if the compiler or glibc is chanced, one has to > > > rebuild > > > chapter 5 anyhow. Looking at the packages in chapter 6, there is > > > just > > > only 2x extra time involved to compile them. Especially when > > > there is > > > no > > > testing done, as was possible under the previous releases. > > > > > > Maybe one could explain this a little deeper? > > Isn't "Toolchain technical notes" in "Important Preliminary > > Material" > > enough? Well, maybe not. All we have is: > > "As said above, the standard C++ library is compiled next, followed > > in Chapter 6 by all the programs that need themselves to be built. > > The > > install step of all those packages uses the DESTDIR variable to > > have > > the programs land into the LFS filesystem." > > > > Maybe better would be something like this: > > "As said above, the standard C++ library is compiled next, which > > completes the cross-compilation toolchain. Next, in Chapter 6, all > > the > > programs that need themselves to be built. The install step of all > > those packages uses the DESTDIR variable to have the programs land > > into > > the LFS filesystem." > > > > Also, in chapter six' introduction: > > "This chapter shows how to cross-compile basic utilities using the > > just > > built cross-toolchain". > > > > Maybe add a sentence about impossibility for testing at the end of > > "Those utilities are installed into their final location, but > > cannot be > > used yet" > > > > Pierre > > > So, if I read above reaction correctly, the only reason for having > chapter 6 is the use of the DESTDIR variable?
Hmmm, not exactly. It's rather: chapter 5 for the cross compiler and its libraries, chapter 6 for building basic tools using this cross- compiler. Actually, the libraries in chapter 5 make use of DESTDIR too... > > Sure, I understand that the tools build in chapter 5 are now used to > build programs/libraries which need to run on the target machine > itself. > The whole set of chapter 6 and 7 can be copied to the target > machine, > from where you can start building the final code with chapter 8 and > higher. This, however, needs some augmentation to the end of chapter > 7 > and start of chapter 8 or insert a new chapter 8 "Preparing the > target > machine". > > NOTE: this can help some users who's intended target machine is a 32- > bit > x86 and their host machine is a x86_64. Just as a show case when > addressing none x86(_64) architectures in some future version. Hmmm, we are trying to get the multilib build to work ATM. But I've never thought of building for 32 bit on a 64 bit machine... > > Anyhow, the presented text make things - in my view - a little more > clear for the intended audience. Will think a little more and try to come with something even clearer (needed in view of your understanding why chapter 6 from my first answer :) Pierre -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
