Making the math libs went well. Once I got the i686 architecture in GMP, the other two picked that up without prompting.
For gcc, this time I removed the "exit $PIPESTATUS" from "make check", intending to keep my script running. I saw nothing exciting in my log.test. The only glitch was where the checks in 6.17 say: "grep -B4 '^ /usr/include' dummy.log This command should return successfully with the following output: #include <...> search starts here: /usr/local/include /usr/lib/gcc/i686-pc-linux-gnu/4.7.1/include /usr/lib/gcc/i686-pc-linux-gnu/4.7.1/include-fixed /usr/include", what I got is: /usr/lib/gcc/i686-pc-linux-gnu/4.7.1/include /usr/local/include /usr/lib/gcc/i686-pc-linux-gnu/4.7.1/include-fixed /usr/include Does this need to be fixed? (Hopefully in some way so it wouldn't happen again.) -- Paul Rogers [email protected] http://www.xprt.net/~pgrogers/ Rogers' Second Law: "Everything you do communicates." (I do not personally endorse any additions after this line. TANSTAAFL :-) -- http://www.fastmail.com - Access all of your messages and folders wherever you are -- 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
