Jeremy Huntwork wrote:
Gerard Beekmans wrote:
--snip--
This is a bit off-topic, but this discussion has triggered another
thought. With CLFS at some point (whether you decide to chroot or
boot) you're going to be building the remainder of the book natively.
At that point does CLFS really need to maintain separate instructions
on how to do that? In short, do they need to ever worry about UID/GID
etc? We could chop off that entire section in CLFS and point users to
chapter 6 of LFS to finish up their native build.
Less redundancy, less maintenance, less worry about conflicts. I guess
there is the various arch issues and packages specific to those, but
CLFS could give general notes for each arch and instruct users to
return when done with LFS chapter 6 to build any arch-specific packages.
--
JH
It would be a lot of trouble to go through and ditch post-chroot/boot
from CLFS and point to LFS Ch6.
The problem with cutting out CLFS after you chroot or boot is that for
the x86_64 multi-lib, the LFS Ch6 does not work (ie, you need to build
32-bit and 64-bit versions of the same packages with varying library
directories and build instructions. Just have a quick look at
http://www.linuxfromscratch.org/clfs/view/cross-lfs/x86_64/ to see some
of the differences) Not to mention the various architecture specific
packages, patches and fixes (theres quite a few after a quick glance at
the various books for CLFS).
It would be easier to cut out Ch6 onwards of the LFS book and splice Ch5
(and previous) into the CLFS pre-chroot/boot section and use the x86
build path to finish it off...
Emu
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
