On 3/18/12 6:44 PM, Bryan Kadzban wrote: > Well, from the comments in the book, it's not libc; it's crt1/crt0/crtn, > or whatever the files are named these days.
Yes, you are correct, it's the start files it can't find. I was just being imprecise. > One other thing I'm concerned about is enabling multilib for my own > builds, if we do this setup, without having to go all the way into the > CLFS (IMO-)crazy with cloog and ppl and eglibc and whatever else. I > might be able to get away with simply removing --disable-multilib, and > then building all the libraries twice with the proper -m flags, but it's > been a while and I don't remember for sure. :-/ (OTOH it may be quite > a while before I rebuild this system.) Yes, multilib still works well, just remove the lib64 symlinks, make real lib64 dirs, kill the --disable-multilib flags and build 32-bit glibc. I find I don't typically need any other 32-bit libs - but that may be just my needs. JH -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
