On Thu, Jul 20, 2017 at 06:48:20PM -0400, Isaac D. Cohen wrote: > > But then I decided to try, just to make sure, and redo the second pass > of gcc with --enable-threads. After doing that I redid the compilation of > glibc and got the same error. So that doesn't seem to be the problem. >
That error is not at all common in LFS, so maybe nobody knows the answer. I think you said that gcc wasn't working when you went into chroot, so you rebuilt pass2 binutils and gcc. That destroyed any evidence that might have been available (you didn't mention the error message, or whatever led you to realise it wasn't working). Your current problems suggest that maybe there were other errors - my first guess was that g++ had not been built correctly, but that is just a guess. Unless anyone has any easier suggestions, I'm going to suggest that you start over. If your lfs user still has the command history, look at that before you restart, in case anything now jumps out and says "whoops!". For a restart, save all the sources and patches so that you don't need to download them again. Then make a new filesystem for /mnt/lfs. If your distro insists on mounting the new filesystem under /media, then get a root shell (you need that anyway during the build, even on ubuntu which hates letting users get root shells) and bind it to /mnt/lfs (mount --bind : man mount). Then rerun the stuff to setup the environment, including any checks. For the build, please remember that you need clean source for each package, so remove the extracted directories when you move on to the next package (particularly binutils and gcc, but also relevant for all packages in chapter 6 that were also built in chapter 5). And I hope your next attempt is successful. ĸen -- I live in a city. I know sparrows from starlings. After that everything is a duck as far as I'm concerned. -- Monstrous Regiment -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
