Hey All:
Need some feedback on how exactly we're going to handle 64-bit in the Cross-LFS book, so bring on the comments! ;)
Basically, the cross-lfs book will be multi-arch, in that, once you've picked the architecture of the target system, the one you're wanting to run LFS on, all instructions will be geared toward that arch. For an example of how that will work, see http://linuxfromscratch.org/~jhuntwork/multi-arch/
However, now that 64-bit is gaining popularity in a number of archs, the question of how to handle that in the book comes up. For example, are we building both 32-bit and 64-bit libs (multilib), or are we just building 64-bit? If multilib, are we creating a /lib64 and keeping /lib 32-bit, or will it be /lib32 and /lib as 64-bit? Should we allow the user to decide which of these options or paths to take and support all decisions?
My personal feeling is that on 64-bit archs we should have one default way of handling it, and not really take the extra effort to explain all alternatives. There are too many ways to go and the book would become a great deal more complex were we to do that. Furthermore, the user should learn enough by the default path to choose a slightly altered path if he/she desires.
So, in a nutshell, my opinion is that we should do multilib as a default for 64-bit archs with /lib and /lib64 directories.
This has not yet been decided on for the book (which is why I'm asking this question here), so if you have an opinion or comment on the above, *please* reply here. We *need* your feedback in order to make a decision.
Thanks!
-- Jeremy Huntwork -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
