Jeremy Huntwork wrote: > 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! ;) > > > 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? Multilib would be the best. Using /lib for 32-bit and /lib64 for 64-bit, the other way gets to be a little bit hackish. > > 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 would be the way I think it ought to be done as well, having tried to tackle a multilib build a while back things work much better that way.
-- Thomas LFS User : 4729 / Linux User : 298329 kitt - Powered by: Linux 2.6.9-1.667 08:22:44 up 3 days, 22:05, 2 users, load average: 0.25, 0.51, 0.34 -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
