On 01/05/2016 05:16 PM, Paul Rogers wrote:
The only thing I can think to do now is to start all over again at the
beginning of chapter 5, and double check that I am following all the
directions correctly. But before I do that, I wanted to post the above
errors to see if by chance anyone might have an idea what is going
wrong with the build.
Richard, I don't think I'd go to that extreme "right off the bat".
1- I'd first question the host system gcc. Are you sure it meets the
prereqs? I'd make sure of that.
2- If that patch makes your glibc compile work, then that suggests that
maybe your host compiler is missing that itself. Check its Changelog.
Is there an update available?
3- Next I'd question if the host compiler had gotten corrupted. I think
I'd reinstall that, update if possible, and try your make check again.
4- If that fails, try recompiling glibc-2.22 again and checking again.
I think there may be some hope that the packages you've already built
that didn't hit this bug are OK. You wouldn't know for sure, of course.
But I think the problem may well originate in your host system, not what
you've built.
Thanks for your suggestions. I have some new information, and I
think your suspicion that something is amiss with my host
system is probably correct. I've been suspecting that I may
have a memory problem, so I downloaded a program called
memtest86 to test my RAM. This program detected errors in
one of my RAM plugin modules. I was able to replace the
module, and running memtest86 again showed no errors. So
now I think I do have to build lfs-7.8 over again. Hopefully
this time it will build without problems, now that the
memory problem is fixed.
I'm not sure what you mean in #2 above about the patch.
You are referring to the largefiles patch, right? Do
you mean that glibc or gcc in my host system, which is
lfs-7.6, also needs to be patched?
Richard
--
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
