Jeremy Huntwork wrote: > As an aside, the effects of their not having a /lib64 dir or symlink > seems to be that if I want to use a CLFS system as a host, I *must* use > their pure64 patch. I tried a build last night without using that patch > and just using --disable-multilib and appropriate symlinks and gcc pass1 > failed when it got to stage1 of the bootstrap. I didn't get the > opportunity to add a /lib64 symlink and test it further... > > I suppose that if the above is correct this also means that your native > build expects a /lib64 dir or symlink on the host?
This is confirmed. Adding /lib64 and /usr/lib64 symlinks to a CLFS host enables gcc to bootstrap in pass1 without using the pure64 patch. -- JH -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
