Jeremy Huntwork wrote:
So, in a nutshell, my opinion is that we should do multilib as a default for 64-bit archs with /lib and /lib64 directories.
Care to explain the basis on which you're forming that opinion for those of us paupers not able to afford such exotic hardware? :)
Well, I'm certainly no expert on the subject, (yet! ;) ), I'm learning the process as I go, but from what I can see so far, gcc, when building for 64-bit expects there to be a /lib64 directory. To try to force it to do /lib32 and /lib requires a lot of wrangling. But there are others who are more experienced with this than I, which is why I need comments and feedback. Certainly, if there are FHS or other standards, we would want to try to stick to those.
As far as going multilib by default, it seems reasonable to me that you'd want to have both libs on a system for packages that perform better with one or the other.
-- Jeremy Huntwork -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
