Hello again,
now I completed the lfs build, and I had a very nasty problem with
your handling of /lib64 and the new approach, that the toolchain is no
longer isolated in /tools.
After solving my problem in the previous discussion, I started my
packaging at the beginning of Chapter 7 now by package everything in
$LFS at the end of Chapter 6 to an initial package.
So everything works well, the libs and programs in $LFS are rebuild in
Chapters 7 and 8 and are captured by my packaging method correctly. So,
in theory, after completing Chapter 8, I don't need anything from my
initial toolchain package, so I should be able to remove it from my
package chain.
But by removing it, i render my new system unusable, since /lib64 is
created in the toolchain phase in Chapter 5.5.1 only and is never
touched again in any following package. So by removing my initial
toolchain package I remove /lib64 and the very important link in it.
Of course this is easy to fix but I want to suggest to add the creation
of the directory /lib64 in chapter 8.5 (when generating the final
glibc), because otherwise your whole final system depends on something
created in the toolchain.
By just adding the directory /lib64 and the 2 links in my glibc-package
does the trick and my system is running again without anything from the
toolchain (as it should be).
bye,
Patrick
--
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
