On Thu, 17 Jan 2019 14:46:33 -0600 Bruce Dubbs <[email protected]> wrote:
> Typically the solution for errors like you describe is to start over > and be more careful following the commands in the book. Yes. This is why it's all scripted. Doing some searches I found this quote in the mailing list, perhaps by you: Quote from LFS mailing list: "Usually if your interpreter is wrong with gcc or binutils after chroot, it means that gcc source and/or build directories were not removed before the next build." And there was an error at the end of one script. Each package is built starting with a script template but that one was missing a final popd which prevented from erasing a gcc build directory when done. I think that was the culprit. I rebuilt ch5, and without mount the VFS or doing anything else like creating directories and such, too eager to find out I guess, I chrooted in the result, went to /tools/bin/ and executed gcc directly there. It worked. I will step back, mount the VFS, create the directories and all that, and chroot again. I can't imagine that the file systems and directories would mess this up. Ah, I haven't done the stripping of the binaries either by the end of ch5. Will do that of course. That a directory did not get deleted was one thing. The other is that the following statements in gcc 2nd pass were really standing on their own lines, one per line, in the script: CC=$LFS_TGT-gcc CXX=$LFS_TGT-g++ AR=$LFS_TGT-ar RANLIB=$LFS_TGT-ranlib Now it's all one line: CC=$LFS_TGT-gcc CXX=$LFS_TGT-g++ AR=$LFS_TGT-ar RANLIB=$LFS_TGT-ranlib ../configure [...] (email client formatting may prevent seeing it as one line) -- 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
