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?
Best stay /lib /lib64, trust me... I'm still working on hackery for gcc to provide the other if so desired but it is not that high on my agenda as of yet...
Plus, if you go the other way, expect pain with pre-compiled stuff such
as Nvidia drivers, and you have to hack X which defaults to lib64 if doing a 64bit build
So, in a nutshell, my opinion is that we should do multilib as a default for 64-bit archs with /lib and /lib64 directories.
Sounds fair enough... Though if we have a multilib book and a uni-arch book, we can cater for both straight64 and multilib...
Do try to take into account that some arches (mips) have 3 or more ABI's when structuring the book... not sure of the sanest way to do that...
Can you re-render the same page multiple times with different output using different entities each time? (/me is not strong on XML) ie: a template for the build instructions that shouldn't need to change, just different entities set when it is called?
Showing my ignorance here, so be kind ;-)
Regards [R]
-- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
