> During the glibc tests, I was able to find the cause of the errors > with a quick search, so I knew they weren't a problem. I am unable to > determine whether the errors are serious or not. > > The following is the result of piping "make check" to "grep FAIL":
I think the most prudent assumption is errors in glibc are "significant until proven otherwise". But I fear you've "grepped-away" too much. My recommendation would be to "tee" the console log during "make check" (and "CMMI" too for that matter) to files, then use "less" to actually look at what else the tests are trying to tell you with "/Error". -- 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 - Does exactly what it says on the tin -- 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
