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
Ok, so, it seems that most of you are alright with this method, including the script-master himself, which is always a plus. ;)
I'm finishing up general build instructions for the sparc architecture atm. When that's finished, I'll get the order/layout for Sparc64 since I have the hardware here. We'll do multilib with a /lib64 and /lib. When I have that basic structure in place, I'll add in a x86_64 instruction set (minus sparc-specific stuff) and let you all take a crack at it. Should be happening within a week or two, I hope.
Sounds fair enough... Though if we have a multilib book and a uni-arch book, we can cater for both straight64 and multilib...
Let me get at least the first way down and in book form and we'll see what happens after that. ;) Can't really comment on your XML ideas because I'm not very versed there either.
-- Jeremy Huntwork
-- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
