Jeremy Huntwork wrote:
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
I installed my system to /lib with 64-bit only, no multilib. I did have to modify a few files for gcc, glibc, perl and only a few others. It really was not a big deal, a few patches would do the trick. The only strange thing gcc did was to put the libgcc files into /lib64 no matter what I did, of course someone with more experience could correct this. Since I was experimenting anyway, I crossed my fingers and copied them in /lib and did not have a problem. Most of the other packages expected to find files in /lib so no changes were needed. The only problem I had was with grub, with is not 64-bit compatible, so I fell back to lilo, which was no problem.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
