On Mon, Aug 06, 2007 at 08:30:55PM +0200, Tobias Vogel wrote: > Ok, i think i found the problem. While it is linking to > /lib/ld-linux-x86_64.so.2 > the directory /lib is empty, but the file is located in the /lib64 > Is this correct, that /lib is empty? Or is it supposed to contain data? > Is it supposed to be a symbolic link to lib64? > *All* of the libraries are supposed to be in /lib or /usr/lib on pure64. That is why we kick the toolchain packages to persuade them we don't want to use lib64 (e.g. the temporary symlink for ld-linux.so.2 and then the sed on ldd while we install glibc).
At this point (just after glibc), the only libraries in the final system have come from glibc, so it looks as if you missed the instruction that says: Tell Glibc to install its libraries into /lib: echo "slibdir=/lib" >> configparms Maybe you can recover from this by moving the libraries from /lib64 to /lib. Try that, I don't see why it wouldn't work - if you wanted to backtrack and rebuild glibc correctly (after deleting from /lib64) you would need to alter the specfile back to /tools/lib - doing that from outside chroot using vim would be safer than developing your own sed, but rebuilding glibc would be a lot of extra work. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce _______________________________________________ Clfs-support mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
