> I was able to replace the module, and running memtest86 again showed You know that sometimes just the connectors will cause problems? Seen that more times than I can count, albeit more in the olden days. The first thing to do when it seems like there's a memory error is just pull out all the modules and push them back into the same places, and retest! That wipes off corrosion, and recreates a good elecctrical connection.
After doing the memtst, the next thing I'd run is e2fsck -f on all the filesystems. > 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 don't think I'd be so ready to toss all that work. I think there's a decent chance that what you've done so far never saw that bad memory, and it's good to go. So I'd rerun the glibc build and see if that works now. Those libraries will be used as you proceed, and if they're corrupt you'll soon find out and can THEN start over. If things keep working, you "dodged a bullet". ;-) > 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? If it was 7.6, probably not, but I wasn't quite sure what the host was, so was just speculating about possibilities. -- Paul Rogers [email protected] Rogers' Second Law: "Everything you do communicates." (I do not personally endorse any additions after this line. TANSTAAFL :-) -- http://www.fastmail.com - The professional email service -- 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
