This is a continuation from here: http://linuxfromscratch.org/pipermail/lfs-dev/2007-July/059737.html
Starting a new thread because the last one was getting unwieldy and had several different topics running through it. Greg, the host I was working from was a current CLFS development snapshot. All that 'ls -ld /l*' shows me is: drwxr-xr-x 5 root root 2696 2007-07-19 16:35 /lib 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? I found a Ubuntu CD and a spare partition, so I'll be using them as a host for my next test. I may also run a DIY build, just to familiarize myself more with your current setup. -- JH -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
