I had issues with this before, but the first one is believed by me to be solved. THis would be my fourth time at this point for something to go wrong.
I will attach the my make log.
https://onedrive.live.com/redir?resi...347110C1%21415

Log created with command:

Did you follow the book exactly?

Exactly, as in using the wget list and using md5sum list. As well as,trying my best not to make a typo. I can give you guys more information and a referring thread to a previous problem.

If you followed the book exactly then it shouldn't be coughing up an error during the make (building) session.

Try using make -j1, make -j2, or make -j3 and see if it builds. I did hear through the LFS grapevine of some issues with make at times during compile if you use too many parallel processes at once.

A standard make is my fallback option. I know that if I follow the book, I shouldn't have issues. My problem is that this is my fourth go-round in the build process, and each time sometime go wrongs. Typically, the binutils. First time was accidentally setting the "CC=..." in the main build terminal. The rest have been related to binutils.

By any chance are you running an AMD CPU from the A4-APU, Athlon II, or Phenom II series?

First Generation Haswell i5, 16 GB RAM, AMD HD7000 series Graphics

Chapter 6 glibc should only fail under these conditions:

1. Improper mounting of virtual file systems and file systems.

2. Improper chroot login.

3. Improper Linux-headers installation.

4. Improper temporary symlinks to tools systems, and file system directory creation.

Unless you also corrupted the tools chapter 5 build, it should be okay.

Anyway to check for an corrupted Chap 5 build?

Not really, but if you stripped the wrong files it could have if you stripped the static libs.

Well, I rebuilt after cleaning it and got it to boot, now the c character does not exist which quite annoying when c cannot be typed and it happens in chroot. Sounds to me to put in a new thread, which I will do.

Solution I ended using:
1. clean out /usr/local of host
2. update to testing version of host
3. clean LFS directory
4. update book to 20140723
5. try again
6. have LFS distro appear empty
7. try try again
8. find out that partition was not mount and mount
9 copy what I did to right part.
10. have the files mysterious reappear while copying
11. reboot into lfs
12. not able to login due to no password
13. make root passwd
14. reboot into lfs

Are you using a non-US keyboard layout?

Yes, standard US layout

The soulution to my latest issue was to remove the first line of /etc/inputrc which was the command to generate itself (cat ...).
Now I know what happens if you do that.